insert error - SQL Server Forums

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

Other Forums

MS Access

insert error

Author

Topic

subin_m
Starting Member

1 Post

Posted - 2003-11-12 : 09:19:53

The following insert statement causes me to loose sleep and hours of wasted time it has 95 fields minus one (first one ) which is an auto number.
therefore I have left it out.The polexp (third field) has datetype and the error leaves the cursor after the 2nd comma .i.e on the third field (polexp)

I have no idea why . I tried quoting it ...no success .Can some one help me please?Thanks in advance

INSERT INTO Policy ( tipyn, tipnum,polexp, agcycd, company, poleff, polexp2, fname1, lname, addbusname, addname1, addlegent, phone, addr1, zip, lglenty, [billing plan], pyplan, constate, facbus, yrriskndt, glcode, tip, liabcovg, liabtype, medpaycovg, medpaytype, nofaultcovg, nofaulttype, Uninsmtrcovg, uninsmtrtype, ph6ydsmgetype, towcovg, towtype, grgkprscovg, grgkprstype, ulgrgkprscovg, ulgrgkprcovgtype, cmbbipdcsl, cmbded, cmbdedmod, sepded, sepdedi1, sepded12, propdmg, rt2sue, bilmtperacc, bilmtperper, bijded, propdmglmt, prodmgded, polliabtype, numbparts, brcovgend, hircarst1, hircarcsthire1, harcarst2, hircarsthire2, nownemps, nownpars, nownextcov, nfltfrstpart, nfltcomblmts, nfltspltlmts, addmedexp, worklosslmt, funexplmt, adddeathlmt, extmedbene, perinjprotlmt, addpiplmt, mibroadopt, deathbene, addperinjprolmt, pipfunbene, pipinclmt, pipmedlmt, medpaylmtperper, uninsmtrcsl, uninmtrstk, uimcombded, undrinsmtrcsl, undinsmtrstk, phydamhircarspecs, speccauslmt, phydamcomp, phydmacomplmt, phydamcompded, phydamcolded )
values(False,,,,,,,,,,,,,,,,,,,DE,False,,,,False,,False,,False,,False,,False,,False,,False,,False,,,,,,,,,,0,,0,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,)

jsmith8858
Dr. Cross Join

7423 Posts

Posted - 2003-11-12 : 16:50:30

leave out the fields you do not wish to insert into. It will also make your SQL much easier to read !!!

i.e., instead of

INSERT INTO Policy (F1,f2,f3,f4) VALUES (1,,,3)

you say

INSERT INTO Policy (F1,F4) VALUES (1,3)

get it? Much easier and shorter! Plus, the first scenerio (which is what you are trying to do) is not valid SQL syntax.

- Jeff

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources