Tezcatlipoca
Registered User.
- Local time
- Today, 08:14
- Joined
- Mar 13, 2003
- Messages
- 246
The Situation:
I have the misfortune to have a seagull for a manager (i.e. he who flies in, makes a lot of noise, craps over everything, and then leaves). To make matters worse he is convinced that he is exceedingly computer literate, despite all evidence to the contrary. To date, the witless wonder has managed to inadvertently delete, move, or rename just about everything that I've not managed to hide or lock on our office PC, with the result that the first half hour of my working day is clearing up after his hour's worth of destruction he likes to engage in every morning before anybody arrives.
Normally this isn't too much of a problem, but he has recently noticed that I have password locked a number of buttons on the database I wrote for the office, and has asked why. My explanation that it was easy to make an error, or accidentally delete records, if you didn't know what you were doing, was met with the response of 'Well, it won't matter then, because just you and me will have access. So everything will be alright, won't it?'.
The Proposed Solution:
To keep the imbecile happy, I've decided to try and write some kind of 'kiddy-filter', to ensure that he can enter records, but in no way alter or delete the records already there.
My requirements for this are twofold, both of which I'm a little uncertain about how to approach the coding:
Step One - Adding
Firstly, I need to set up some kind of form where he can enter data in each field. My problem is that opening the form I use to view the data in ADD mode enables a user to EDIT any of the records as well as ADD new ones. This is no good. I need something whereby he can simply enter data and, once done, can submit that data to the records. I can then come in later and clear up any mistakes he's made.
Step Two - Masking
To ensure he enters data to a certain standard, is it possible for me to define all the variables for a certain field, and to prevent that field being filled until they are met (so say, for example, the field holding the product name can be one of four choices, can I stop him entering everything but one of those four?).
Any ideas?
I have the misfortune to have a seagull for a manager (i.e. he who flies in, makes a lot of noise, craps over everything, and then leaves). To make matters worse he is convinced that he is exceedingly computer literate, despite all evidence to the contrary. To date, the witless wonder has managed to inadvertently delete, move, or rename just about everything that I've not managed to hide or lock on our office PC, with the result that the first half hour of my working day is clearing up after his hour's worth of destruction he likes to engage in every morning before anybody arrives.
Normally this isn't too much of a problem, but he has recently noticed that I have password locked a number of buttons on the database I wrote for the office, and has asked why. My explanation that it was easy to make an error, or accidentally delete records, if you didn't know what you were doing, was met with the response of 'Well, it won't matter then, because just you and me will have access. So everything will be alright, won't it?'.
The Proposed Solution:
To keep the imbecile happy, I've decided to try and write some kind of 'kiddy-filter', to ensure that he can enter records, but in no way alter or delete the records already there.
My requirements for this are twofold, both of which I'm a little uncertain about how to approach the coding:
Step One - Adding
Firstly, I need to set up some kind of form where he can enter data in each field. My problem is that opening the form I use to view the data in ADD mode enables a user to EDIT any of the records as well as ADD new ones. This is no good. I need something whereby he can simply enter data and, once done, can submit that data to the records. I can then come in later and clear up any mistakes he's made.
Step Two - Masking
To ensure he enters data to a certain standard, is it possible for me to define all the variables for a certain field, and to prevent that field being filled until they are met (so say, for example, the field holding the product name can be one of four choices, can I stop him entering everything but one of those four?).
Any ideas?
