>>Hi Fox gurus :)
>>Me again, after all these years :)
>>Question: When I try SET IDENTITY_INSERT ON|OFF, I don't get a trappable error, but the error is still being raised on the ODBC side and the SET is not set. Has anybody have any experience and especially - luck, in dealing with issuing SET statements from VFP?
>>I tried this thing in both VB and VFP, but to no avail.
>>
>>Thanks in advance,
>>
>>Robert.
>I assume you are using SQL Passthrough for this. I ran into problems doing this sometime back. Try sending the SET IDENTITY_INSERT command and your INSERT command via the same SQLEXEC command.
>
>HTH

Hey, thanks for a reply...I thought my messages are never gonna get through!!! I am using PassThrough, but in VB :( That's what the client wants their app developed in. They want to massage the data at will after I'm gone in MS Access, and I can't convince them to use anything but VB. I was also given a specific set of guidelines to use while developing: Set DB = OpenDatabase... Set RS = DB.OpenRecordSet... and that's it. Fortunately, I am given a free hand in terms of stored procedures, views and server cursors, so my life is not THAT miserable :) ... Anyway, have you tried to SET anything through a stored procedure? Please let me know, I am anxious to minimize this spaggetti roll (not sure about the first word :)

Thanks in advance,

Robert.

Some things are better be left unknown...NOT!!!