Help with password-protecting database for edits

[RSW]

Hello,

I designed and distributed a database client to a bunch of users. They have asked me to password-protect it so that anyone can open the database and view the forms, but a password is needed to actually make any updates. I am trying to do this, but everything in Tools--Security is making my head spin. I have actually already managed to somehow lock myself out of my own database, although I have another copy.

How do I set the Workgroup Administrator Files so that they apply to anyone? It wants to put a separate file on my C: drive, but I don't use this database, I distribute it to people who do. (The server is on a share drive, can I put the Workgroup file(s) there?)

What settings do I modify to require *anyone* to need a password to update? Or is that even possible? I don't really want to break up the users into different categories.

If anyone could walk me through this process I would really, really appreciate it.

 

[Dennisk]

workgroups can be tricky, but the standard is to set up a blank db and create an administrator, and two groups. Set the permissions for one group to insert/edit/delete and apply it to all tables. Then create another group with read only permissions.

Keep this db and workgroup safe as you can now copy this to any new db without going through the hassle of having to create it from scratch.

To assign permissions for an individual user just assign them to one of the two groups.

 

[RSW]

Thanks--but does this mean my idea of requiring a password only for updates isn't feasible? Is the only way to apply a password, to require it for opening the database at all?

 

[RSW]

Or--the form in question shows one big record with lots of fields at a time--is there a way to get a pop-up saying "Do you really want to make these changes" or something before moving to the next record?

The users are concerned about someone inadvertently changing data as they're just browsing. But--all users need to be authorized to add or update data when that is necessary.

 

[Dennisk]

if you want to trap changes to a record on a form use the before update form event and check if the data has been changed

if me.dirty then
if msgbox ("The record has changed, do you wish to apply Changes",VBYesNo) = vbNo then

cancel=true
endif

 

[RSW]

That sounds like it will work. Thank you!!

 

[RSW]

if you want to trap changes to a record on a form use the before update form event and check if the data has been changed

if me.dirty then
if msgbox ("The record has changed, do you wish to apply Changes",VBYesNo) = vbNo then

cancel=true
endif

Hi everyone,

I have implemented this and it works great, EXCEPT that if you are using the form, accidentally change something and don't know what it was, you have no option to just move away from the record without changing it. You actually have to close the database to not save the record.

Does anyone know how to modify the above such that, if you click a record selector and answer "No" to the above question, it takes you not back to the current record, but to the next one without saving any changes you made?


Thanks in advance.