We often get this error when we use ODBCs pointing to DBCs and two users try
to open an ADO connection simultaneously - one of them fails.
Having trawled the internet for a solution, I've found only an obscure support
article from Microsoft confirming that this is a bug. They suggest merely
trapping it in an error routine and doing an infinite number of retries.
Having recreated this error in code, I've discovered that the 'retry' only
works once the 'dominant' connection is finished, so this is useless - our
application can have multiple users opening and closing these connections
throughout the day, and this much traffic is bound to cause several pile-ups!
Configuring the ODBC to point to a drectory instead never fails - are there
any drawbacks to using this method instead of the DBC one, or does anyone
know how to fix the original problem?