users can enter database without joining workgroup!

[rutica]

I have a Access 2003 database called HA_PAD.mdb on a shared drive. My colleague created a workgroup HA_PAD.mdw file. But I'm not sure if the HA_PAD.mdw was created correctly.

We are asking new users to join the workgroup manually by following the directions below:

Open MS Access. (Via a shortcut under Programs or directly via C: Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE)
Click on Tools on the menu bar
Click on Security in the drop down menu
Click on Workgroup Administrator...
In the Workgroup Administrator menu click on the Join command button
Browse to the HA_PAD.mdw via S:\Program Management\AD Project Health\HA_PAD.mdw
Click OK

The problem is, if the user doesn't follow the directions above to join the workgroup, they can still enter the database.

I have 2 questions:
1). How to force the users to join the workgroup.
2). Is there a way to automatically join them so users don't have to follow the directions above?

Thanks!

 

[HiTechCoach]

The security was not applied correctly.

Second, the data needs to be split with the front end on machine.

Third, it is best to use a shortcut to open the database with the correct work group file as a command line switch. If you joined the work group per your instructions,m the will effect every database used by Access that does not use a shortcut to set the correct work group.

 

[rutica]

Thanks for writing.
I don't think we're ready to split the database. For now, we want the db on the shared drive.

What should I do to make the security correctly applied?

Thanks!

 

[HiTechCoach]

I don't think we're ready to split the database. For now, we want the db on the shared drive.

If you do NOT split the database, then it should NEVER have two users in the database at the same time unless you want to corrupt the database and probably lose some data.

While the Access 2002/2003 seurity model works great, there is a large learning curve to getting it to work correctly. That may be whey it was removed from the new Access 2007 format (ACCDB)

See:
Access 2002/2003 Security Step by Step

The Microsoft Access Security Apparatus


I would recommend doing more testing before trying to place into production.