MDW file

[Derek Wittman]

Good morning,
I have created a shortcut that opens Access (2000) and my database (Startup opens to my main form) using my workgroup file (/wkrgrp). However, I have found that when I open Access with the default workgroup file, I'm automatically ADMIN with no required password (and I believe that any of my users - or anyone else in the company! - can probably do the same thing. All it seems to take is for the user to know to view files of HIDDEN type and pull up the database inside their Access application (as opposed to the command line options).

How can I make this better? Further, my shortcut has the full path to the database and the workgroup in it. Any suggestions on how I can remove the temptation to look it up, and increase security?

Thank you!
Derek

 

[Immanuel Sibero]

Hi Derek

Your database doesnt appear to be secured properly. MS Security is quite
elusive. Your observations re: logging in as Admin with the default
workgroup file (system.mdw) and the fact that anyone else with their default
workgroup files can do the same thing are correct.

How was the database secured? Was the security document followed exactly?

http://support.microsoft.com/default.aspx?kbid=207793


HTH,
Immanuel Sibero

Good morning,
I have created a shortcut that opens Access (2000) and my database

(Startup opens to my main form) using my workgroup file (/wkrgrp). However,
I have found that when I open Access with the default workgroup file, I'm
automatically ADMIN with no required password (and I believe that any of my
users - or anyone else in the company! - can probably do the same thing.
All it seems to take is for the user to know to view files of HIDDEN type
and pull up the database inside their Access application (as opposed to the
command line options).

How can I make this better? Further, my shortcut has the full path to the

database and the workgroup in it. Any suggestions on how I can remove the
temptation to look it up, and increase security?

 

[TC]

A properly secured database can only be opened with the correct workgroup
file. If you can open it with any other workgroup file, you have not secured
it correctly. Get an original copy of your database, from before you started
to try & secure it. Then find the Access security FAQ (or similar document),
& follow all the steps >precisely< - adding & omitting nothing.

HTH,
TC

Good morning,
I have created a shortcut that opens Access (2000) and my database

(Startup opens to my main form) using my workgroup file (/wkrgrp). However,
I have found that when I open Access with the default workgroup file, I'm
automatically ADMIN with no required password (and I believe that any of my
users - or anyone else in the company! - can probably do the same thing.
All it seems to take is for the user to know to view files of HIDDEN type
and pull up the database inside their Access application (as opposed to the
command line options).

How can I make this better? Further, my shortcut has the full path to the

database and the workgroup in it. Any suggestions on how I can remove the
temptation to look it up, and increase security?

 

[Derek Wittman]

Thanks, Immanuel and TC. I forgot the step with removing ADMINS group from the Admin user. Admin user has NO rights now. I've got an Access guru who's travelling quite a bit for work, and I've asked him to try to bust into it.

I appreciate the help!
Derek

----- TC wrote: -----

A properly secured database can only be opened with the correct workgroup
file. If you can open it with any other workgroup file, you have not secured
it correctly. Get an original copy of your database, from before you started
to try & secure it. Then find the Access security FAQ (or similar document),
& follow all the steps >precisely< - adding & omitting nothing.

HTH,
TC

Good morning,
I have created a shortcut that opens Access (2000) and my database

(Startup opens to my main form) using my workgroup file (/wkrgrp). However,
I have found that when I open Access with the default workgroup file, I'm
automatically ADMIN with no required password (and I believe that any of my
users - or anyone else in the company! - can probably do the same thing.
All it seems to take is for the user to know to view files of HIDDEN type
and pull up the database inside their Access application (as opposed to the
command line options).database and the workgroup in it. Any suggestions on how I can remove the
temptation to look it up, and increase security?

 

[Derek Wittman]

Update. I've gotten the User-Level Security Wizard to work finally. My company has the install CD in the lab, so I had to get the lab tech to put it in the drive. Worked like a charm. I'm still unsure of Step 10 in Section 1 - What are the steps to secure a database...

I'm in Access 2000 and didn't have to manually remove the Open/Run permission from the database.

And I learned that, before I was able to run the wizard, I was not able to Change Owner from Admin to myself.

Derek

----- Derek Wittman wrote: -----

Thanks, Immanuel and TC. I forgot the step with removing ADMINS group from the Admin user. Admin user has NO rights now. I've got an Access guru who's travelling quite a bit for work, and I've asked him to try to bust into it.

I appreciate the help!
Derek

----- TC wrote: -----

A properly secured database can only be opened with the correct workgroup
file. If you can open it with any other workgroup file, you have not secured
it correctly. Get an original copy of your database, from before you started
to try & secure it. Then find the Access security FAQ (or similar document),
& follow all the steps >precisely< - adding & omitting nothing.

HTH,
TC

Good morning,
I have created a shortcut that opens Access (2000) and my database

(Startup opens to my main form) using my workgroup file (/wkrgrp). However,
I have found that when I open Access with the default workgroup file, I'm
automatically ADMIN with no required password (and I believe that any of my
users - or anyone else in the company! - can probably do the same thing.
All it seems to take is for the user to know to view files of HIDDEN type
and pull up the database inside their Access application (as opposed to the
command line options).database and the workgroup in it. Any suggestions on how I can remove the
temptation to look it up, and increase security?