@arnel, The OP wants to prevent saving a record if it is incomplete. The only RELIABLE way to do that is to put the validation code in the form's BeforeUpdate event so the save can be cancelled if there is an error. Putting validation code in control events works for some things but NOT for validating presesce. If focus never enters a control NO control events fire. If the control is entered but the control isn't dirtied, the BeforeUpdate event does not fire so you cannot reliably use control level events to ensure that any control that requires a value has one.
The form is bound. It is already wrapped in a transaction. If the form were unbound you could use a transaction around your update code but unless the fields are defined as required, there is no getting around the requirement to validate.
@
mrahulkanth, I have told you how to control whether or not a record should be saved and others have concurred and even supplied code. You can of course add a save button if you wish and force the users to use it but I think that is over kill. You want to avoid sending spurious messages to the user. All that does is to train them to click to get past the message and they stop reading the messages which causes them to ignore important ones. Just because a user jumps through the hoop and presses your save button doesn't remove you of the obligation to actually validate data. As the developer you have to ensure that data is as valid as you can. Dates (all of them) need to be checked at a minimum for a valid range. 3/6/202 is a valid date as far as Access is concerned but unless your app is dealing with ancient history, this date would not be logically valid and yet it is a very common typo that you can prevent if you take the effort. If the only valid options are Blue and Red, then the user should not be able to enter Green. You can't do anything about him entering Blue when he meant Red but you've done your duty just getting that far. Every app is different so I can't tell you what you need to edit and what rules you should employ, your users would be a bid help for this. For the Blue/Red issue, I would use a combo that only presents the two choices. That means you can avoid having to edit data entered via combos. The only edit would be if the app required a value then you would ensure that a value was entered but any value from the combo would be valid so as long as you have set limit to list to yes, then you don't have to go any further.
In the BeforeUpdate event, when you find an error, you can give the user two options but make sure your message is clear. One option is to return and fix the error, the second can be to cancel the save. If the user elects the cancel option, you would use Me.Undo to back out the users edits so he can gracefully leave the form.
