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?