OPENCURRENTDATABASE - Error 7866 / Office 2003 and security.

[L. Scott M.]

Hi,

1) We are on a restricted environment - Access Macros Security have
been restricted to Medium only on all machines. This would not be a
problem if the message "Opening c:\db1.mdb This file may not be safe
if it contains code that was intended to harm your computer. Do you
want to open this file or cancel the operation ? Cancel/Open/More
Info" would appear as documented.

2) The problem first appeared when they pushed Office 2003 to all the
machines.

3) Development seats, machines blessed with Admin rights (Still Medium
Access Macro Security), recieves the expected message, selecting "open"
the user can continue.

4) The User seats hit the OPENCURRENTDATABASE, displaying the Error
7866 "Microsoft Access cant open the database becaue it is missing or
opened exclusively by another user." and the application dies. The
database is not missing and is not opened by another user, much less
exclusively - we built another application with only the
OPENCURRENTDATABASE command in it and the problem repeats.

We assume that there is a setting somewhere (Registry) to fix this
problem but since all our machines are "crippled" to some extent or
another we cannot even attempt to discuss a solution. This VB 6.0
application is scheduled to be obsolete in three years or so we would
like it to limp along till then.

TIA
Scott M.

 

[Guest]

Had the same problem. Check out "About Microsoft Jet Expression Service
sandbox mode" at
http://office.microsoft.com/en-us/assistance/HP010446591033.aspx.

Once unsafe expressions were blocked the problem went away. A security
warning message box still opens but all the users have to do is click the
open to continue with the code execution.