Access 2003 - Sandbox Mode - Setting Macro Security to Low

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a project that was in place with access 2002 and had no issues. The
customer upgraded everythign to access 2003 and I am now getting the "unsafe"
expressions errors. This new feature seems like a real nuisance but that is
neither here nor there.

My problem is that this application is run in a terminal server environment.
There are 8 terminal servers that use it and depending on the load at the
time a user runs this app, it could put that user on any of the 8 servers.

I went to each server and put the macro security level to low but because it
is a terminal server, it seems that this setting is user specific. It is not
practical for me or their staff to go to each server for each user and set
the security level to low.

Looking for options of turning this feature off. I found a microsoft
article that does a registry edit but my client is hesitant to turn this off
this way. I have also found an article that if you digitally sign the code,
this feature should not affect you either.

Are there any other options? I don't have a digital signature and it looks
like that costs at least a couple hundred dollars. Does anyone know why
Microsoft would have put this in there? I understand the intent but the
delivery seems to really be a bad solution for the developer.

Any input on ways to turn this off in a terminal server environment. How
are other developers handling this? Any and all ideas are appreciated.
 
Hello "TarponZeke"

TarponZeke said:
I have a project that was in place with access 2002 and had no issues.
The customer upgraded everythign to access 2003 and I am now getting
the "unsafe" expressions errors. This new feature seems like a real
nuisance but that is neither here nor there.

My problem is that this application is run in a terminal server
environment. There are 8 terminal servers that use it and depending
on the load at the time a user runs this app, it could put that user on
any of the 8 servers.

I went to each server and put the macro security level to low but
because it is a terminal server, it seems that this setting is user
specific.
It is not practical for me or their staff to go to each server for each
user
and set the security level to low.
Click to expand...

Configuring Access to run in sandbox mode will also be user specific.
But I'd prefer this rather than setting the security level to low.
Looking for options of turning this feature off. I found a microsoft
article that does a registry edit but my client is hesitant to turn
this off this way. I have also found an article that if you digitally
sign the code, this feature should not affect you either.

Are there any other options? I don't have a digital signature and
it looks like that costs at least a couple hundred dollars.
Click to expand...

The easiest way is to create a certificate yourself using selfcert.exe
on your developer machine. If you are developing in a team, you could
install Windows 2000 or 2003 certificate services on a server and issue
a code signing certificate that can be used by all developers of your
company. But nevertheless, every user of your database application
will once have to "trust all code that is signed with your certificate".
 
Back
Top