David There is a possibility that this is caused by an anti-virus program putting a lock on (the technical term) the .ldb lock file. This is not your Legacy database itself, but associated with it. If this is the cause, then you can tell your ant-virus software to exclude scanning of MSACCESS.EXE files But I only know this for Symantec's DLP (Data Loss Prevention) client software. It may not apply to other "domestic" virus checkers.
Even if this is NOT the problem, you may have to delete the .ldb file. Check the Legacy Help web page - I think there is a specific article there. The file is recreated by the "Access database engine" which Legacy uses, and deleting it does no harm. Cathy Pinner or Brian Kelly may have some observations about Error 3045? Ian Thomas Albert Park, Victoria 3206 Australia -----Original Message----- From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On Behalf Of David Dearth Sent: Sunday, 23 April 2017 10:49 AM To: LegacyUserGroup@legacyusers.com Subject: Re: [LegacyUG] V9 Error Code 3045 Thank you Robert and Bob... yes I have tried rebooting. I have since confirmed that this is indeed a MS Access (which I believe Legacy uses) error code and not Legacy's (it is not listed in Legacy's error list either). A Google search turned up many hits on this. I will investigate further and get back with the group on what I find out. Dave -- LegacyUserGroup mailing list LegacyUserGroup@legacyusers.com To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/legacyusergroup@legacyusers.com/
