Jet40 SP8 and Access W2K3

[MrPhil]

I've installed SP8. Why does ACCW2K3 insist on reminding me, upon
attempting to open an MDB: 1: that unsafe expressions are not blocked
(I don't care; this is an internal protected app);
2: that when I say "no", a hugo largo window pops up, advising me that
I have to install SP8 to block unsafe expressions (I've already a)
installed SP8 and b) told Access that I don't want to block them; and
3: of a final security warning that restates what the previous two
windows warned about, and gives me one final chance to abort (if I'm
come this far, you're damn right I want to open the file!!)?

This is preposterous. Why all the hoo-hah about SP8 when I've already
installed it? Explanations and a fix, please.

[SA]

Mr. Phil:

1.) Reinstall sp 8 if you haven't already from a clean boot.
2.) Blocking unsafe expressions really is recommended since VBA and DAO can
be instantiated from many other places outside access and functions like
Kill can have disasterous results.
3.) Even when you've done all the above, unless your Security settings in
the Tools->Macros-> Security Settings is set to low, A2K3 will still prompt
you with a one time warning about potential security issues when opening ANY
db whether it contains VB code or not. The only way around that is to
create a self signed digital certificate and add that to all your dbs and
indicate when opening a db the first time that you "trust" yourself and your
own certificate.
--
Steve Arbaugh
ACG Soft
http://ourworld.compuserve.com/homepages/attac-cg

"MrPhil" <pd************ ***@yahoo.com> wrote in message
news:f8******** *************** ***@posting.goo gle.com...

I've installed SP8. Why does ACCW2K3 insist on reminding me, upon
attempting to open an MDB: 1: that unsafe expressions are not blocked
(I don't care; this is an internal protected app);
2: that when I say "no", a hugo largo window pops up, advising me that
I have to install SP8 to block unsafe expressions (I've already a)
installed SP8 and b) told Access that I don't want to block them; and
3: of a final security warning that restates what the previous two
windows warned about, and gives me one final chance to abort (if I'm
come this far, you're damn right I want to open the file!!)?

This is preposterous. Why all the hoo-hah about SP8 when I've already
installed it? Explanations and a fix, please.

[MrPhil]

"SA" <~f***********@ nspm.com> wrote in message news:<bn******* ***@ngspool-d02.news.aol.co m>...

Mr. Phil:

1.) Reinstall sp 8 if you haven't already from a clean boot.
2.) Blocking unsafe expressions really is recommended since VBA and DAO can
be instantiated from many other places outside access and functions like
Kill can have disasterous results.
3.) Even when you've done all the above, unless your Security settings in
the Tools->Macros-> Security Settings is set to low, A2K3 will still prompt
you with a one time warning about potential security issues when opening ANY
db whether it contains VB code or not. The only way around that is to
create a self signed digital certificate and add that to all your dbs and
indicate when opening a db the first time that you "trust" yourself and your
own certificate.
--

Ugly. Just plain ugly. We have ~650 Access users (and I mean
base-level users). Now I have to tell them to set security? Or to
apply digital certificates to the hundreds of MDBs we use?

How about someone just supplies me with the registry key for the
security setting, and we'll hack it in our login script? This other
folderol is for the birds.

[TC]

"MrPhil" <pd************ ***@yahoo.com> wrote in message
news:f8******** *************** ***@posting.goo gle.com...

"SA" <~f***********@ nspm.com> wrote in message

news:<bn******* ***@ngspool-d02.news.aol.co m>...

Mr. Phil:

1.) Reinstall sp 8 if you haven't already from a clean boot.
2.) Blocking unsafe expressions really is recommended since VBA and DAO can be instantiated from many other places outside access and functions like
Kill can have disasterous results.
3.) Even when you've done all the above, unless your Security settings in the Tools->Macros-> Security Settings is set to low, A2K3 will still prompt you with a one time warning about potential security issues when opening ANY db whether it contains VB code or not. The only way around that is to
create a self signed digital certificate and add that to all your dbs and indicate when opening a db the first time that you "trust" yourself and your own certificate.
--

Ugly. Just plain ugly. We have ~650 Access users (and I mean
base-level users). Now I have to tell them to set security? Or to
apply digital certificates to the hundreds of MDBs we use?

How about someone just supplies me with the registry key for the
security setting, and we'll hack it in our login script? This other
folderol is for the birds.

Isn't it just the thing for customers! "Hey, opening this app you got from
TC Enterprises will destroy your PC" ...

TC