Atomic Shrimp
Humanoid lifeform
- Local time
- Today, 10:07
- Joined
- Jun 16, 2000
- Messages
- 1,954
I've got an application where certain parts of certain forms should be invidible or disabled by default, only being enabled if the user logging in has sufficient rights, etc.
As developer, I have of course assigned one of my test IDs to have these rights - if I log in as this user, then switch to design mode to tweak something, then close the form, not only do my tweaks get saved, but the visible and enabled properties of the assorted restricted-access controls also get saved in their available state - so the next user to log on sees them whether or not he/sh really should.
I can of course control this by adding an Else clause to the conditions that test for the access rights, and set the properties, but I'm sure I never had to do this in previous versions of Access and that only changes I explicitly made to properties, at design-time, were saved.
Is this behaviour configurable?
As developer, I have of course assigned one of my test IDs to have these rights - if I log in as this user, then switch to design mode to tweak something, then close the form, not only do my tweaks get saved, but the visible and enabled properties of the assorted restricted-access controls also get saved in their available state - so the next user to log on sees them whether or not he/sh really should.
I can of course control this by adding an Else clause to the conditions that test for the access rights, and set the properties, but I'm sure I never had to do this in previous versions of Access and that only changes I explicitly made to properties, at design-time, were saved.
Is this behaviour configurable?
