"Read only" users: What's the best way?

[gusbrunston]

I haven't gotten to the part in the book about security. Can I just copy a data input form and make the copy "read only" ? I'm sure there's a better way. I know I can "yes" and "no" the form property sheet. With two forms, I could "yes" one and "no" the other. But I'm sure it's not good "form"! Do I need to get into passwords and all that?
Thanks. (-:

 

[MichaelRed]

Just my opinion, but don't get into Ms. Security in any casual sense. Read the book. Try te samples/examples on a 'throw away' database. Do it at least twice. "It" has PROPERLY been referd to as "Byzintine" (sp?). It works WELL - sometimes ALL To well!

It is a good lock for the cheap stuff, but like some combination locks - if you loos or mis-assign the combination(s) there is no way back. While the Wizz will bake a back-up of your db, it is/can be frustrating to do a lot of work on a production system and need to do it over because of seemingly trivial mistakes.

I always set up the most basic security possible, and then make changes through programatic interfaces.


MichaelRed
redmsp@erols.com

There is never time to do it right but there is always time to do it over

 

[ghubbell]

Hi Gus,
In agreement with Michael, you could do a wack of reading and testing on this and this alone. I clearly remember my first encounter and actually phoning MS to say how awkward I found their setup. Over time you can learn to live with it and eventually manage it. I have in the past created security methods that of course require a user name and password to start the database (really basic), and then control the users by a more familiar user table with a few "switches" (yes/no fields). When a form opens it might run a little function to see if user Gus is allowed to edit or only read, and adjust the form's settings accordingly. Are you getting some ideas?! Gord
ghubbell@total.net

 

[MichaelRed]

I find the Assignment of individuals to "Groups" and the consequent use of Group permissions on the database objects to be much easier to maintain than the individual permissions. But it DOES require that you read and understand the security model. Which, as Gord says is not a trivial task. On the other hand, if you are going to assign permissions manually, are you SURE that the assignees are not able to get to the table and change their own permissions? Are you really confident that you can (and will) be able to set the appropiate permissions at all levels on an individual basis?

.......

and a few more questions along the way!

(No, I AM N[red]OT[/red]/ a Microsoft fan/dealer/owner ...

I just happen to really NEED security on a db once and got all the way through the MDW thingggyyyy (with the help of one on the several third party books on MS Access) and find that, although it is somewaht arcane, once it is set up it does work.


MichaelRed
redmsp@erols.com

There is never time to do it right but there is always time to do it over