Harry,

Let me know if Jim's reply didn't get you unconfused.

>The field in question is for an account reference. If the field is empty, it pops up a list of available references. If the user can't find the one he needs, he can enter a new reference. The valid clause then checks the address file, spots the fact that the reference does not already exist and then and there offers the user the opportunity to add the new address. If the user says 'Yes' then the address form is run and a new record added with the new account ref.
>
>It is from this point on that the keypress (PGDN) may be required to shift focus between the address form controls and the command buttons. And because the form has been run from within the original valid clause, I get the error. How else can I provide that functionality without using the original valid? The only thing I can think of is shifting it away from field level validation to record level but a) that would be less useful and b) it would still be a 'valid'.