I don't use record validation rules much to tell you the truth, usually do this at a UI level. Basically you would have to deal with correcting the errors within the function, using oldval(), giving a custom message with messagebox(), and always returning TRUE from it since invalid data simply wont be allowed to go through. Otherwise whenever you return FALSE, the error messagebox you mention will appear, and I don't know how to override it, but probalby someone else here does, you could start a thread on that specific question, you'll get better and faster responses on such questions because they require simple straight forward answers.

>My bad. I overlooked the whole thing, it was the simple "RETURN .F." that I left out. I have it before and then erased it (don't know why). It is working now and am happy with it.
>
>Now, I like to ask the next step/question. Since the error messagebox isn't that user-friendly ("Record validation rule is violated"), how can I change the message while keeping the standard route of options that appears with the messagebox (OK and Revert) and take out the Help button. I may have to create a new messagebox, thats fine, how?
>
>>Well, then you're missing a step, I wish I could post screen shots, I thought it was very clear, but simply put, if whatever is in the Record Validation field evaluates to False, you can't move the record pointer.
>>
>>

>>case CASE ALLTRIM(UPPER(authtype)) = "VISA"
>>   if empty(fund)
>>
>>       RETURN .F.
>>
>>   endif