Velociraptor said:
A loose connection remains the most likely cause but I have experienced this
on several occasions:
1) This almost never occurs if you have Access fronting an SQL database -
MDB's seem much more susceptible.
Absolutely. One reason would be because there is much less network
traffic. Another is that Access sends a small amount of constant
network traffic every second. When dealing with SQL Server it likely
doesn't.
2) Make sure the database is compacted and as small as possible. My
experience is that the bigger the MDB file, the more likely is the error.
Sure.
3) The problem is even more likely if you are sharing an MDB with several
users over a network.
Why?
If possible, forget Access as a shared DB, use SQL 2000 or MSDE 2000 for the
back-end and this class of error (assuming it is not caused by hardware)
will disappear.
Sure. but SQL Server is more work to install and learn. There can
also be a very significant investment in time to convert from an
Access BE to SQL Server.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm