Security Warning Message

[Guest]

I have 5 Access databases on a sharedrive being used by multiple users. How
do I turnoff the Security Warning Message that pops up before the users can
open the database? I have gotten so many complaints about this.

 

[Jeff Conrad]

See this page on my site for info:

http://home.bendbroadband.com/conradsystems/accessjunkie/macrosecurity.html

--
Jeff Conrad
Access Junkie - MVP
http://home.bendbroadband.com/conradsystems/accessjunkie.html
http://www.access.qbuilt.com/html/articles.html


in message:

 

[TC]

Probably covered by Jeff already, but: look for posts containing the
word "automationsecurity", in this newsgroup, from me (TC). This is by
far the easiest way to suppress all the warnings, if your database is
not secured, and your PC allows VBScript.

HTH,
TC

 

[Jeff Conrad]

Yep, you're on the page TC.


--
Jeff Conrad
Access Junkie - MVP
http://home.bendbroadband.com/conradsystems/accessjunkie.html
http://www.access.qbuilt.com/html/articles.html


in message:

 

[Guest]

TC,this sounds like a very good solution,but the databases are on a
sharedrive bing accessed by multiple users across various states. I can't see
how it would work for this situation. The database should not be open all the
time,but only when needed.

Next,if you still think this is a good solution,how do I get the vbscript to
run,will the other user have to click a button or something to get the script
to run everytime they want to open the database? They are not going to like
that either.

 

[Guest]

TC,I think I answered my on question. Place the vb file on the share drive
for each database,right

 

[TC]

Cyndy, be aware that you should not have many people sharing a single
MDB file at the same time. This is commonly believed to make it more
likely that your database will become corrupted.

Ideally, your database should be split into a so-called "front end/back
end" structure. The front end (FE) database contains just the tables -
nothing else. The back end (BE) database contains all the queries,
forms, reports, macros & modules, and /links/ to the tables in the BE.

There is a single copy of the BE on the server. But each user has a
seperate copy of the FE, either on their PC, or in a seperate folder on
the server.

You'ff find lots more information about FE/BE structures by googling
this & other Access groups.

HTH,
TC

 

[TC]

Yes, you would need one vbscript file per database. Just put them on
the server. Then, instead of double-clicking file blah.mdb on the
server, the user simply double-clicks file blah.vbs, to avoid the
security warnings..

HTH,
TC