I have inherited maintenance and support duties for several large production Access 2000 databases. Most of the daily corruption issues have been solved by eliminating the cross-reference table links amongst each Db and placing the critical tables into separate back-end databases thus, lessening the impact to all other databases when one or another crashes. However, problems remain although, I have isoloated the main problem to be in the Accounting Db but cannot pin down which form(s)/table(s) are causing this Db (about 75 megs with about 8 concurrent users) to crash and require compact/repair almost every hour. Network, driver and service pack issues have been eliminated so, that leaves only one thing: the Db application itself.
My question: Is there a way to configure/implement global error logging on the database so that I can determine when (or who is causing) the critical error to actually trigger the corruption, without writing a generic Db error trapping routine and then code calls to that routine from every form in the Db?
I've looked and cannot find such a facility if it indeed exists in Access (it certainly does in the AS/400 world).
Any suggestions would be greatly appreciated.
Respectfully,
Michael
My question: Is there a way to configure/implement global error logging on the database so that I can determine when (or who is causing) the critical error to actually trigger the corruption, without writing a generic Db error trapping routine and then code calls to that routine from every form in the Db?
I've looked and cannot find such a facility if it indeed exists in Access (it certainly does in the AS/400 world).
Any suggestions would be greatly appreciated.
Respectfully,
Michael
