I'll try the short version first. I get an error -2147217871 (timeout expired) on an insert to a table with 28 fields. I have several smaller tables in the same db that work fine in performing deletes and inserts. What is hopefully a clue is that inserts to the larger table work at the click of a key if I have just resized any of the larger table fields, saved, and then run my code. The code will work two or three times consecutively, then it breaks with the timeout expired error, and nothing less than changing a field size again makes the larger table insert work.

Just for funsies I have set the ADO command timeout very high to see what would happen. It has been running for about an hour. No error yet, but no execution either. I have set no locks that I am aware of.

Thanks in advance for any help.

Sounds like there might be a lock on some data. Can you see anything suspicious in the manager or the SQL logs?

--

Joe (Microsoft MVP - XML)

I posted to another individuals similar problem that I had gone into Enterprise Manager (on a private development server) and killed all lock processes I found. My code then worked.

The only place I have stipulated locks is on edited records using MS Access's 2007 default project setting in Options. I suspect that the lock is not being released because I am in development and working specifically on the code that when it breaks before proper termination leaves locks in place.

Last evening I had input a dozen records and they all acted as expected. Now, I think I am looking for advise on how to check for active locks and unlocks them on program startup. I am guessing that would be to check for the appropriate error number in my error routine and close the table. Have no idea yet if that is really what I need to do.

Thanks for the reply. I had been messing with this for a week and really did not expect to find a potential answer so soon after posting the inquiry.