Security issue with deployment

[Drew]

i was curious as to weather i needed to include the
workgroup file with the database i created as a package
bc it will not be on one network but on several
computers. Also when i have it on my house network i can
access the database without having to enter name and
password but i do on my other computers.....why is that?
is it bc the one computer is setup as admin on the
network?

 

[Albert D. Kallal]

The way this works is:

if the "admin" user has a password set, then ALWAYS you get a log on.

The "admin" user is the default user here, and the above is the "trigger"
reason you get a logon. So, if you set a password for the admin user, then
you ALWAYS get a logon.

What this means is that if you have only ONE database that is using
security, then you can provide a shortcut to a workgroup file that is going
to be used for ONLY that one database. That way, all other applications
written ms-access don't get a prompt. (so, the default workgroup that you
are joined to would NOT have a password for the admin user, but the most
certainly the ONE application that is secured would also have to provide a
shortcut to the workgroup file during startup)

To eliminate the prompt on those other pc's, you can:

a) remove the password for the admin account,

or

b) create a new workgroup file, and join to that.

However, since those pc's are asking for a password, some application, or
someone along the way set a password for the admin user.