Posted by Erland Sommarskog on 09/13/07 22:14

(teddysnips@hotmail.com) writes:
> Since I had a few minutes to spare, I created a NEW MS Access
> database, linked via the DSN to the database, and created a link to
> JUST the table that was causing the problem. I then created a single
> form which was based on the newly linked table. I opened the form,
> pressed the "New" record button on the Record Navigation group,
> entered a new record, pressed the "Previous" record button and voila!
> the record was saved! I then reverted to the original application and
> it worked! My client was delighted.

At this point, did your mock-up application still run?

Did you try to save twice from the mock-up?

Have you checked if there are any triggers on the troublesome table? My
feeling is that there is a trigger which produces a result set, or even
just a rowcount, and the application fails to consume that. When you try
to save a new, friendly ADO will open a new connection behind your back,
because the first connection is busy. But the second connection is blocked
by the first.

But that's really only a guess, and keep in mind that my knowledge on
Access is about zero.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

[Back to original message]