Password on Access Database?

[Jorge Biquez]

Hello.

I'm developing a simple application with VB and access database.
Today my application crashed and I found that one of my users just opened
the database under Access and changed some values on some of the tables because
he thougth that was easier ....anyway. How can I protect a database so the
final user can not open it from access?

Thanks in advance.

JB

[Robert Gelb]

You can password protect the database, but the password on Access97 is
pretty easy to break. A lot more difficult to Access2k

--
Robert Gelb
www.vbRad.com
Source Code, Tips, Tricks, Components


"Jorge Biquez" <jbiquez@icsmx.com> wrote in message
news:3ae9bf05$1@news.devx.com...
>
> Hello.
>
> I'm developing a simple application with VB and access database.
> Today my application crashed and I found that one of my users just opened
> the database under Access and changed some values on some of the tables
because
> he thougth that was easier ....anyway. How can I protect a database so the
> final user can not open it from access?
>
> Thanks in advance.
>
> JB

[Mike Bristol]

Though I agree with Robert, that MS-Access 97 security isn't perfect, I have
found that it is adequate to prevent nosy users from getting into tables
directly from Access and messing the data up.

To do this, use the 'User Level Security Wizard' from the Tools...Security
menu. In the resulting dialog, it asks which objects you want to secure,
and also shows the Workgroup File that is currently being used.

BIG TIP: avoid modifying your system.mdw in the Windows directory. This
should always be left as-is so you can go back to Access with no security.


To create a new .mdw file, use the Workgroup Administrator Applet that comes
with MS-Access (wrkgadm.exe in the windows\system directory). Click the
Create button to make a new one. Put the new .mdw file in the same directory
as the .mdb file you are wanting to protect (this will make remembering where
the .mdw file is much easier). I usually name the .mdw file with the same
prefix as the .mdb file to eliminate confusion.

When the new file is created, you are automatically enrolled in that workgroup.
By joining a group other than the original one, you are telling MS-Access
that you require a username and password to open the program...it then uses
that user name and password to check the workgroup file (.mdw file) to determine
that you are a valid user. To undo this, just re-join the original workgroup
in the windows\system directory.

Now that you have a new workgroup file to use, go back into MS-Access and
set a password for the Admin account. This will prevent anyone from getting
into the db using that account without a password. WRITE THE PASSWORD DOWN!!
From the Tools...Security...User and Group Accounts menu, create a new account
for yourself and be sure to add it to the Admins Group. Now close MS-Access
and then reopen it, logging in as the new account you just added.

From the Tools...Security...User and Group Accounts menu, remove the Admin
user from the Admins Group.

Now run the 'User Level Security Wizard' from the Tools...Security menu
again. The dialog should now show that you are going to mess with the new
file. Set security on the database objects you wish to protect (I always
set all of them and use user-level permissions to control access). It will
ask for a name for the DB, name it whatever, and then you will have to rename
the unsecured (old) DB and name the newly created secured DB what the old
one was. Add an account for your application to get at the data with.

You don't need to join the workgroup file on your computer to access the
database unless you want to use MS-Access...to use VB, just set the connection
string property of the ADO connection object (or equivalent properties on
the data control).

Good Luck!!

Mike Bristol, MCSD


"Robert Gelb" <robertgelbNOSPAM@zdnetonebox.com> wrote:
>You can password protect the database, but the password on Access97 is
>pretty easy to break. A lot more difficult to Access2k
>
>--
>Robert Gelb
>www.vbRad.com
>Source Code, Tips, Tricks, Components
>
>
>"Jorge Biquez" <jbiquez@icsmx.com> wrote in message
>news:3ae9bf05$1@news.devx.com...
>>
>> Hello.
>>
>> I'm developing a simple application with VB and access database.
>> Today my application crashed and I found that one of my users just opened
>> the database under Access and changed some values on some of the tables
>because
>> he thougth that was easier ....anyway. How can I protect a database so
the
>> final user can not open it from access?
>>
>> Thanks in advance.
>>
>> JB
>
>

[Jorge Biquez]

Hello MIke.

Thanks a lot for all the detailedinformation about how to protect Access
97 databases. I'll protect mine, thanks a lot.

JB

"Mike Bristol" <mike.bristol@anl.gov> wrote:
>
>Though I agree with Robert, that MS-Access 97 security isn't perfect, I
have
>found that it is adequate to prevent nosy users from getting into tables
>directly from Access and messing the data up.
>
>To do this, use the 'User Level Security Wizard' from the Tools...Security
>menu. In the resulting dialog, it asks which objects you want to secure,
>and also shows the Workgroup File that is currently being used.
>
>BIG TIP: avoid modifying your system.mdw in the Windows directory. This
>should always be left as-is so you can go back to Access with no security.
>
>
>To create a new .mdw file, use the Workgroup Administrator Applet that comes
>with MS-Access (wrkgadm.exe in the windows\system directory). Click the
>Create button to make a new one. Put the new .mdw file in the same directory
>as the .mdb file you are wanting to protect (this will make remembering
where
>the .mdw file is much easier). I usually name the .mdw file with the same
>prefix as the .mdb file to eliminate confusion.
>
>When the new file is created, you are automatically enrolled in that workgroup.
> By joining a group other than the original one, you are telling MS-Access
>that you require a username and password to open the program...it then uses
>that user name and password to check the workgroup file (.mdw file) to determine
>that you are a valid user. To undo this, just re-join the original workgroup
>in the windows\system directory.
>
>Now that you have a new workgroup file to use, go back into MS-Access and
>set a password for the Admin account. This will prevent anyone from getting
>into the db using that account without a password. WRITE THE PASSWORD DOWN!!
> From the Tools...Security...User and Group Accounts menu, create a new
account
>for yourself and be sure to add it to the Admins Group. Now close MS-Access
>and then reopen it, logging in as the new account you just added.
>
>From the Tools...Security...User and Group Accounts menu, remove the Admin
>user from the Admins Group.
>
>Now run the 'User Level Security Wizard' from the Tools...Security menu
>again. The dialog should now show that you are going to mess with the new
>file. Set security on the database objects you wish to protect (I always
>set all of them and use user-level permissions to control access). It will
>ask for a name for the DB, name it whatever, and then you will have to rename
>the unsecured (old) DB and name the newly created secured DB what the old
>one was. Add an account for your application to get at the data with.
>
>You don't need to join the workgroup file on your computer to access the
>database unless you want to use MS-Access...to use VB, just set the connection
>string property of the ADO connection object (or equivalent properties on
>the data control).
>
>Good Luck!!
>
>Mike Bristol, MCSD
>
>
>"Robert Gelb" <robertgelbNOSPAM@zdnetonebox.com> wrote:
>>You can password protect the database, but the password on Access97 is
>>pretty easy to break. A lot more difficult to Access2k
>>
>>--
>>Robert Gelb
>>www.vbRad.com
>>Source Code, Tips, Tricks, Components
>>
>>
>>"Jorge Biquez" <jbiquez@icsmx.com> wrote in message
>>news:3ae9bf05$1@news.devx.com...
>>>
>>> Hello.
>>>
>>> I'm developing a simple application with VB and access database.
>>> Today my application crashed and I found that one of my users just opened
>>> the database under Access and changed some values on some of the tables
>>because
>>> he thougth that was easier ....anyway. How can I protect a database so
>the
>>> final user can not open it from access?
>>>
>>> Thanks in advance.
>>>
>>> JB
>>
>>
>