I have a form created in my access database and was wondering if there is anyway to write a macro, or anything else to limit access of just the form to a specific group of people. The database contains many queries and tables that a lot of associates need to view and use however this one form needs to be limited to only a specific group.. Any suggestions?! Thanks!
Limiting access to forms
- Thread starter huskies
- Start date
boblarson
Smeghead
- Local time
- Today, 00:32
- Joined
- Jan 12, 2001
- Messages
- 32,040
1. Check out this sample here:
http://downloads.btabdevelopment.com/samples/misc/LoginSample.zip
2. Don't post the same question multiple times on the forum. It is highly frowned upon.
http://downloads.btabdevelopment.com/samples/misc/LoginSample.zip
2. Don't post the same question multiple times on the forum. It is highly frowned upon.
Re: Limiting users access
Different ways and depending on whether the data base it split and used on a network.
But if the different people are using the same computer you could do the following
1) Base the form on a table that has no records
2) Then have code or a macro on a label or button that changes the record source of the form to the query you currently use.
3) Place an unbound textbox on the form and here you would enter a password. In the code or macro that is used to change the record source have a condition that depends on the value entered in the unbound textbox. I would also put a SaveRecord action at the start of the code or macro.
This will mean someone can open the form but not see any records or do anything meaningful (or nasty) on the form. Although if the form has buttons that perhaps open other forms then you might have those made invisible on opening the form. Then the code or macro you use to change the record source could also make those buttons visible.
Different ways and depending on whether the data base it split and used on a network.
But if the different people are using the same computer you could do the following
1) Base the form on a table that has no records
2) Then have code or a macro on a label or button that changes the record source of the form to the query you currently use.
3) Place an unbound textbox on the form and here you would enter a password. In the code or macro that is used to change the record source have a condition that depends on the value entered in the unbound textbox. I would also put a SaveRecord action at the start of the code or macro.
This will mean someone can open the form but not see any records or do anything meaningful (or nasty) on the form. Although if the form has buttons that perhaps open other forms then you might have those made invisible on opening the form. Then the code or macro you use to change the record source could also make those buttons visible.
Last edited:
