Access 2003 Runtime (Developer Edition) - startup errors?

[pat_nospam]

So I've been packaging my product, but have noticed with 2003 it has security in place that puts up all kinds of warnings that are quite annoying when the program is started. It talks about the unsafe expressions that all programs could have and asks to confirm this.

It's not my application, as it happens with _all_ databases I am trying to open via Access 2003, even brand new ones with only a table or something in it. I can alter the settings via Macros->Security Settings to get rid of the first two error messages, but Access 2003 _always_ asks the following error message:

Any idea how to turn this off on both Access 2003 full version and the runtime version I am now distributing with my program? (especially the runtime version, as it makes an annoying Access-type splash screen pop-up to my otherwise pristine program )

Thanks in advance,

Patrick

 

[pat_nospam]

Wow - nevermind. Just found the long and short of the Office 2003 Digital certificate run around.

Looks like I'll have to shell out $400 to Verisign for the Digital Certificate to "sign" my work.

http://office.microsoft.com/assistance/preview.aspx?AssetID=HP010397921033&CTT=98

http://www.verisign.com/products/signing/code/

 

[SteveC24]

HAHA! I have just been having this problem myself.

OK - there are 2 ways around it that I have found.

1. Create a self-signed digital certificate, and provide your users with instructions how to accept it, and install it on their system.
That is quite a long process...they have to run it once, accept all the warnings, then run it again, and they can then choose to always trust code from this certificate signer (You) - you can then get into the properties for the certificate, and install it on the local machine.
But as I say, it is a long winded process.

ALTERNATIVELY:

2. You can muck around with the registry, and alter the users settings. This is not a preferred option with most people, nor was it with me, but the benefits of it outweighed the negatives.
Basically, you are altering the security settings for macros as VBA for Access as a whole on that system.
You need to go into the registry, and go to:
HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0\Access\Security

If security isn't there (which I think it should be), create the key yourself. Then you need to make a DWORD value called "Level", and in the value for it, enter 00000001.

I believe it is OK for me to do this, as long as I tell the user in detail why and how it is done. Also, I give them instructions how to set it back (just delete the Level value). This way, if they want their security levels higher, they can set it back...but they have to put up with the annoying messages.


I hope that answers your questions...after weeks of searching for information myself, I know how difficult finding info can be...anything else you want to know, please don't hesitate to ask!

 

[pat_nospam]

Hmmm, the registry key solution may do the trick, but I need to know how to set this key by the "Additional Registry Key" feature in the Access 2003 Developer Package Wizard for the runtime solution. The problem is, that the runtime version deployed on peoples machines doesn't give them an option to set the macros to low and be packaged, and I don't want to have to set a registry key after installation manually by the user.

I'm still worried I'm going to have to shell out the $$$ for a Digital Certificate...

Any idea if I can add an "Additional Registry Key" that will default the macro security in the runtime version to "Low"?

Thanks for the assist with this new security hassle

 

[ghudson]

I do not have an answer for your problem since I am not using Access 2003 yet but I do have a warning for you.

Your solution of modifying the users registry setting might be a quick fix for you but you will be modifying a security setting that will affect any database that the user opens with Access 2003. Sure your db might be safe and secure but what if the user opens a db that has malicious code? Their security is turned off [by you] and they will not know that a db has any VBA or macros when they open it. Not as extreme but that is kinda like turning off their anti-virus software just so one file will open without any warnings.

Just a thought that you should consider before you alter a users registry. Normally a programmer does not alter a users computer "settings".

 

[SteveC24]

I agree with ghudson, this is why I make it clear I have done it, and give instructions on how to undo it. (I also plan to make it an option in the database to just click a button and it will delete the reg key, but that will come later).

If you are distributing the Access 2003 runtime, you must have the Developer Extensions whatsit, that comes with Microsoft Visual Studio .NET 2003. You can use that to make an installer - with that you can put in registry keys as you like.
Alterntively, if you use the package wizard that comes with the developer extensions, that has the option to add registry keys I believe.

HTH

 

[pat_nospam]

Well, I'm not going to go the registry route - so I'm back to square 1, with the $400/year certificate.

I saw something funny on slashdot.org this morning, that there had been so many complaints about this very issue that in Office 2005 the security will be totally internal by self certification, not third party purchases.

In the meantime, I have a barely used version of Office 2003 Developer/Visual Tools that I would be very willing to trade for a used copy of Windows XP Developer if anyone is interested.

Thanks again guys for the help.

 

[SteveC24]

Hiya,

Have you looked into the self-signed certificate?

 

[pat_nospam]

Yeah But since this will be distributed all over the place, and not just to a local group of users, I don't think it's very practical to include instructions of how to sign us as a "trusted source"

I just can't believe M$ would do this.. I already paid $800 for the developer edition of Office 2003, now I have to pay $400 a year to supress some error messages in my runtime package?

Like I said, sign me up for the Office XP Developer version.

 

[SteveC24]

I know what you mean entirely. The only difference is...I don't plan on spending the $400 a year for something that is lost in the digital ether!

I wrote the form into my db today explaining why I am changing their registry, and providing a command button to change it back.

 

[pat_nospam]

Well, I just ordered a copy of Office XP Developer, to avoid this whole situation with 2003's encryption issues.

My only hope is that this thread will help someone else make an educated decision on this software so more money isn't wasted with Microsoft's various "enhancements"

Thanks for all the help in problem solving this issue.

 

[pat_nospam]

Just a quick supplemental link for those who will walk this path behind us.

http://office.microsoft.com/assistance/preview.aspx?AssetID=HA011225981033&CTT=98

This details the Access 2003 security warnings and the "reason" behind their implementation and my frustration (From Microsoft's site).

 

[SteveC24]

Hope you have better luck with XP