Not sure if this applicable to your situation but I've been doing the validation part prior to saving the record back to the table.
A Save button on the form calls a form method that checks and makes sure the user hasn't left required fields blank. If they are blank, I throw up a messagebox informing the user that a Project Number is required, change the backcolor of the Project Number control to yellow, stop the save process, and set focus to that control.
Works fine so far. hth.
>We have a candidate index on the project field in our project table so no duplicate project numbers can be input. However, the users periodically save a blank record causing a uniqueness of index violation the next time they try to input information and append blank kicks in. I've tried establishing validation rules on the table itself, but I can not get any desired results. Any suggestions would be greatly appreciated.
>
>Thanks,
>Amy
Roi
'MCP' Visual FoxPro
In Rome, there was a poem.
About a dog, who found two bone.
He lick the one, he lick the other.
He went pyscho, he drop dead!