Password issue

[YNWA]

Hi,

I have a form called MAIN. This form contains 3 tabs. Tab 1, Tab 2 and Tab 3.

On tab 2 (SUB1) and 3 (SUB2) I have subforms.

On the MAIN form I have code to prompt the user for a password when I try to open the MAIN form. Works fine.

I have code on the Tab Ctrl to prompt for password on Tab 2 and Tab 3. Works fine.

Now my problem occurs when I use my search forms.

I have a search form that is based on the contents of SUB1. When I search, I can double click and open that record. What it opens is SUB1 form on its own. Again works fine. However, it does not prompt for a password as the password on the MAIN form is on the Tab Ctrl and the other password is on the MAIN form itself, not the subform SUB1.

Now I can easily copy the code from MAIN form onto each subform. And when opening via the search double click, I am prompted for a password. Which is great.

However, if I open my MAIN form I am prompted for the password 3 times. Once for the main form like normal, but then again for each of the subforms that now have the MAIN form password code on them.

Is there a way of keeping a password on the subforms without the need to enter it when opening the main form?

Can you password prompt on a double click event of a list box (my search form)?

Any ideas would be great.
Thanks

 

[DavidAtWork]

You may want to rethink your security design. If access to each tab of your main form is to be controlled, perhaps you could create your own levels of access. In other words if 'Jack' has admin access and should be able to see all tabs, then when 'Jack' logs in make all tabs visible.
If 'John' should only see Tab1, then hide the other tabs when he logs in
and so on
The advantage with this approach is that you only have to check their credentials once at point of login and then make visible/available whatever they have permissions to see or use

David

 

[YNWA]

You may want to rethink your security design. If access to each tab of your main form is to be controlled, perhaps you could create your own levels of access. In other words if 'Jack' has admin access and should be able to see all tabs, then when 'Jack' logs in make all tabs visible.
If 'John' should only see Tab1, then hide the other tabs when he logs in
and so on
The advantage with this approach is that you only have to check their credentials once at point of login and then make visible/available whatever they have permissions to see or use

David

It is single desktop database. The password is required in case anyone jumps on the PC at tries to access it.

Also would the above option work in 2010? Can I assign permissions?

 

[DavidAtWork]

If it's only you that uses it, just password the database, why over complicate it

David