Not sure if this should be in the Tables or Forms part of this forum but Forms won.
I have a table which has a field which needs to be filled in. I thought the best way to ensure that this was done was to set Required=Yes.
Now this works without me having to 'trap' it. ie The Form(s) that this field appears on will throw up an access generated error message if it is NOT filled in.
This is great but proving to be a pain in the proverbials because if I'm trying to debug the Form by going into design mode it wants me to enter something in said field. This causes the database to get updated so I end up with a load of spurious data when testing which is becoming a pain as well.
At the moment I've set Required=No and added code to check if field is filled in. This sort of defeats the object. Am I missing something or is this another 'feature' of access (2010 btw).
I have a table which has a field which needs to be filled in. I thought the best way to ensure that this was done was to set Required=Yes.
Now this works without me having to 'trap' it. ie The Form(s) that this field appears on will throw up an access generated error message if it is NOT filled in.
This is great but proving to be a pain in the proverbials because if I'm trying to debug the Form by going into design mode it wants me to enter something in said field. This causes the database to get updated so I end up with a load of spurious data when testing which is becoming a pain as well.
At the moment I've set Required=No and added code to check if field is filled in. This sort of defeats the object. Am I missing something or is this another 'feature' of access (2010 btw).