Will a digitally signed 2003 Access Database get the unsafe experssion
message? Or any warning for that matter?

The user will still get a message (once) asking whether they trust the
holder of the digital certificate. They may be prompted again repeatedly if
any code or macro changes in the database from how it was at the time it was
signed.

--
Paul Overway
Logico Solutions, LLC
www.logico-solutions.com


"Eric" <(E-Mail Removed)> wrote in message
news:14F9C92D-D4EE-4077-8897-(E-Mail Removed)...
> Will a digitally signed 2003 Access Database get the unsafe experssion
> message? Or any warning for that matter?

If the database is not secured & the PC has enabled scripting, try the
AutomationSecurity method. Quick, easy, & no certificate! Google this
group for posts from me (TC) containing that word.

HTH,
TC

TC,
Here is the database command line I need to use to start the database can
you tell me how to put it into your script?
"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "C:\Program
Files\XXX\ABC\123.mdb" /wrkgrp "C:\Program Files\ZZZ\AAA\999.mdw"

Thanks,
Eric

"TC" wrote:

> If the database is not secured & the PC has enabled scripting, try the
> AutomationSecurity method. Quick, easy, & no certificate! Google this
> group for posts from me (TC) containing that word.
>
> HTH,
> TC
>
>

Eric, at present, the AutomationSecurity approach only works for
/unsecured/ databases, as I said in my other post.

Looking at your startup line, it seems your database is secured. It is
possible, but surprisingly difficult, to get this approach working for
a secured database. I've not published a method for doing that yet,
because I have not got it working to my own satisfaction. So, if your
database is secured, you're probably out of luck with the
AutomationSecurity method, unfortunately.

I have some real problems of my own right now, so I won't be able to
post back on this for several days. Sorry if I unintentionally misled
you about my solution; however, I did say before, "If the database is
not secured...".

Cheers,
TC

NP, TC what you provided me was great. But, you are correct I need a solution
for a secured DB. If you have some script you want me to test out let me
know. Where did you find the Object model for Access?
Once again thanks for all your help. Good luck on whatever project you are
working on.

Eric

"TC" wrote:

> Eric, at present, the AutomationSecurity approach only works for
> /unsecured/ databases, as I said in my other post.
>
> Looking at your startup line, it seems your database is secured. It is
> possible, but surprisingly difficult, to get this approach working for
> a secured database. I've not published a method for doing that yet,
> because I have not got it working to my own satisfaction. So, if your
> database is secured, you're probably out of luck with the
> AutomationSecurity method, unfortunately.
>
> I have some real problems of my own right now, so I won't be able to
> post back on this for several days. Sorry if I unintentionally misled
> you about my solution; however, I did say before, "If the database is
> not secured...".
>
> Cheers,
> TC
>
>

Eric wrote:

> NP, TC what you provided me was great.

No probs, glad it helped.


> But, you are correct I need a solution
> for a secured DB. If you have some script you want me to test out let me
> know.

Unfortunately it is a very tricky problem to get 100% correct!


> Where did you find the Object model for Access?

The object model is just the set of objects, methods & properties that
are described in Access Help. These differ slightly from version to
version. Here's a reference for the Access 2003 one:

(long URL follows)

http://msdn.microsoft.com/library/en...HV01049589.asp

> Once again thanks for all your help. Good luck on whatever project you are
> working on.

I'll need it, belive me! :-(

Cheers,
TC