Sandbox and multiple versions of Access

[Koss]

Hi All,

I hope you can help us. We have an Access Mdb that was originally developed in 2003. We provide it to multiple clients. We have a major security issue with it now as our clients vary in the the office base that is installed in their enterprises (that also meaning that we cannot as an external vendor get to each individual access client in the enterprise). This is our problem:

1. When we provide a client that has office 2003 with a secure mdb (trusted certificate) we do not get any security warnings
2. As the originasation is quite big, someone might have Access 2010 installed. Running the mdb file with the Access 2010 client generates a security warning and goes into sandbox mode (refer to this post Turn off code Security Warning Access 2010) the solutions in the post DO not work for this issue. That is an mdb signed running on 2003 then on 2010. When this mdb is opened, the user (if he or she wants to be malicious) is exposed to ALL the code while in the saqndbox mode. By clicking in the navigation pane...

Anyone with a solution.

We cannot ask the clients to all have microsoft access 2003 or 2010. They are simply too big

Please help!

 

[Galaxiom]

Distribute a signed mde file. This will stop any possibility of anyone ever seeing the code.

If the publisher is trusted then there should not be a problem with warnings. Usually there is just one warning on the first time and they can choose trust the publisher and that is the end of it.

The trusted publisher certificate can be distributed using Group Policy. This will stop any warnings.