G
geo
Because of the macro security level that my company uses (a policy that I can
not change), my users are getting the "file may not be safe" security warning
every time they open my Microsoft Access application. In an attempt to
suppress this warning message I tried to use code signing.
Unfortunately, signing introduced an even more annoying problem. Now every
time someone (including me) attempts to start up the application, there is a
roughly 20-30 second pause during which time nothing seems to be happening.
Microsoft Access itself is visible and just appears to sit there, not showing
any signs of life. After this long pause, the application menu (or if I was
using the shift-key bypass then the database window) appears normally. After
this, everything seems to be working just fine and there are no other delays.
Needless to say, my users are not keen on sitting there for half a minute
every single time they need to access the database (which they have to do
frequently throughout the day). If I remove the signature, then the database
has no problem starting up lightening fast (aside from the security warning,
or course).
I tried to follow Microsoft's knowledge base article 828414 (
http://support.microsoft.com/kb/828414) to the letter. I tried removing the
signature, compacting the database and then re-signing. It appears to make no
difference whatsoever. While compacting the database is a good thing and I do
it daily, it just does not seem to have any impact on the half a minute
startup delay.
Any suggestions would be much appreciated.
George
www.inspiredbrew.com
not change), my users are getting the "file may not be safe" security warning
every time they open my Microsoft Access application. In an attempt to
suppress this warning message I tried to use code signing.
Unfortunately, signing introduced an even more annoying problem. Now every
time someone (including me) attempts to start up the application, there is a
roughly 20-30 second pause during which time nothing seems to be happening.
Microsoft Access itself is visible and just appears to sit there, not showing
any signs of life. After this long pause, the application menu (or if I was
using the shift-key bypass then the database window) appears normally. After
this, everything seems to be working just fine and there are no other delays.
Needless to say, my users are not keen on sitting there for half a minute
every single time they need to access the database (which they have to do
frequently throughout the day). If I remove the signature, then the database
has no problem starting up lightening fast (aside from the security warning,
or course).
I tried to follow Microsoft's knowledge base article 828414 (
http://support.microsoft.com/kb/828414) to the letter. I tried removing the
signature, compacting the database and then re-signing. It appears to make no
difference whatsoever. While compacting the database is a good thing and I do
it daily, it just does not seem to have any impact on the half a minute
startup delay.
Any suggestions would be much appreciated.
George
www.inspiredbrew.com