>Thanks for the tips and ideas George. I'll do some testing today with your ideas.
>
Tracy,
Here's one I forgot to mention. The first few lines read like this
>IF TYPE('lcAl3File')= "L" .OR. EMPTY(lcAl3File)
RETURN .F.
ENDIF
Not knowing the what the caller is here leaves me to guess. However, that's never stopped me in the past.:-)
The suggestion is twofold. First, if the call comes from a user entry, check this there (the Valid event) rather than here. Second, if the caller does not require user entry, use ASSERT to make sure that valid values are passed. Since ASSERT isn't compiled into the application, no additional overhead is incurred there. Further, it will help with testing to assure that no method can call it with an invalid value.
George
Ubi caritas et amor, deus ibi est