Security Warnings

[Guest]

I have created a runtime access database using office 2003. When i have
installed it onto a pc with office 2000 and go to run it, i get various
warning messages before getting into the program. How can i make sure that i
dont get these warnings/questions.

many thanks

Simon Reed

 

[Chris Mills]

Would you care to indicate what exact warnings/questions?
Kinda fundamental, right?

 

[Guest]

Hi Chris,
Yes sorry, they are the digital signature warnings you receive when opening
a database.
Not at the right pc at the moment to really tel more than that.
cheers
Simon

 

[Chris Mills]

I'm not aware that has much to do with Office2000 (presumably meaning
Access2000), nor even whether you are trying to run an A2003 mdb on A2000, or
whether you merely mean "some Office2000 is just present". What the hell DO
you mean?

So far as digital signatures are concerned, in A2003, my reading is that you
have to set the macro warning to low, either manually or by programmatic
means. There are plenty of posts on it.

You still haven't really asked a question, with reference to your first post,
much more intelligent than "it doesn't work".

Chris

 

[Chris Mills]

Is it just spurious that you happened to install on a PC with "Office2000"?
This implies you had a problem when installing with Office2000 AND NOT
OTHERWISE. It seems to me likely, your problem is "merely" with A2003 in all
runtime circumstances? Does Office2000 have anything to do with it or not?

Chris

 

[Guest]

Hi Chris,
Thats it - security levels - now here's a question.
Is it possible to set the security level to low when creating the runtime
program at package wizard stage? so that the pc it will be running on will be
set automatically?
(notice the question marks)

cheers

Simon

 

[Guest]

I developed the database using access 2003, I then created the runtime and
installed the runtime version onto a pc which happend to have Access 2000 on
it.
Other than that this was the only reason I mentioned A2000

regards

Simon

 

[TC]

You *really* want your installation package to automatically drop the
user's macro security level?

That is a really, truly bad idea, imho. Not to be rude, but, what gives
/you/ the right to drop the user's macro security level? Will you take
responsibility, if this causes them to get a virus which erases their
hard disks?

If the database is not secured, & the pc has enabled scripting, the
easiest way to suppress the security warnings is with the
automationsecurity property. Google this group for posts from me (TC)
containing that word, for more information.

HTH,
TC

 

[Chris Mills]

As a matter of interest, installs done by www.sagekey.com suppress the warning
messages, though I don't know how they do it. I thought there were previous
posts in this newsgroup on it (sandbox mode), and I thought the effect was to
reduce the security level.

Chris

 

[TC]

They could do it the same way that I suggest; starting the db via a
vbscript which uses the automationsecurity property to drop the
security level of that single invocation (without actually changing the
default level set for the pc).

TC