Printable View
Jet engine has errors like 3260, 3218, etc. for multiuser usages. These are the numbers used with DAO. However, when one uses ADO, the way to trap these errors seems to be more complicated. To begin with, the VBA.Err.Source has to be checked, whether it's "Microsoft Jet...", "ADO.Recordset", or simply "Provider...". Can anybody provide a code snippet that provides a uniform way to trap these Jet Errors while still using ADO?
ADO has its own Errors collection that you can examine in case a runtime error occurs.
Lother,
I know that. The problem is if you use ADO with Jet. VBA.Err.Source may return either "ADO...", "Microsoft Jet", or simply "Provider" and based on the source by doing a little coding you deduce the error number consistent with what is contained in jeterr40.chm.
If I simply use DAO, things will be easier I suppose in terms of error handling. But since ADO is in and I am anticipating of client/server in the future, I have to use ADO. So maybe Lothar you have deep experience with regards to multiuser locking scenarios that use both ADO and Jet you may share.
If you can give me your email address, maybe I can write to you directly if you don't mind.
J. Doratan