Password for Switchboard - Please help...

[khwaja]

I know this question has been often asked but I have yet to see a solution which could cover following two scenerios.

I need to add a password protection to the button in a switchboard used to manage pages/buttons.

I also need to be able to apply a password to a switchboard button lweading to another page of the switchboard (eg View reports to another page of 6-7 reports).

I am comfortable creating a password form and attching it to the button. The issue is once a user provides a correct password or cancels the form, the focus should be back to the switchboard which in case of maitenance button, will not do nothing and in case of reports menu, will open the reports page.

I have really struggled a lot in getting this sorted out and I will request you to help me. Cheers

AK

 

[dvannoy]

Why not use the built in security within access??

 

[khwaja]

I know there has been a fair bit of discussion in this forum about using built in security features and its ability to apply to various levels. But as with everyone, I just don't find it easy to implement. I must admit that whatever I read on the subject, it became very confusing in the end. Perhaps best way would be to use real life situation as an exmple employing a phony network of people. I am sure you will offer some insight on this.

My requirement is very simple as I am not too concerned about people breaking into the system. I just need a deterrant at best. I think Microdoft should look into provinding a mundane security option to people like myself and you will have noticed that there are quite a few such people approaching this forum with a similar request.

If you could kindly suggest a solution to meet my emergent need, I will be grateful.
Cheers

AK

 

[dvannoy]

Your right this is very simple. There really is nothing confusing about the MDW file(security within access)
why not create a "New" MDW file , store it on your network and attach everyone that will access your DB to that file. then within the security you coule create groups and stick users in those groups and then only give certain groups access to your reports menu or ceratin reports. I use this with a very large DB with about 35 users and it works fine for me.

The other solution would be to create tables that would store user names and passwords. then behind your button you could prompt the user for his user name and password, then check the table to validate it. but, why do that?

your best bet would be to use the MDW file.

Hope this helps

 

[khwaja]

My db development generally involves rolling out mutiple copies of db mostly in replicated form), I don't know whether I always need to make MDW files available with dbs. If so, this would make it quite messey. Perhaps, this assumption on my part played a greater role in me resorting to db based password regime which you alluded to in your second point. Please if you have any experience in db exclusive password protection and linking it to switchboasrd, please help me. Cheers

AK