Larry,

The error was very misleading. I found out the hard way that it was actually a field rule violation in LoginHistory file. I should have trapped with aerror() sooner. Oh, well... ):
--->IIF(_triggerlevel>0,.T.,x3seek("GT",ulh_usrfk,"USERS","Usr_PK",.T.)).

I realized that I was entering an invalid user id in my production test. Normally I would get a 'Password is invalid' message but there was some kind of data corruption in my LoginHistory table so that the program let me go past entering the password.

I 'reset' the field validation by removing it and placing it back. That solved the problem.

Thanks for all your help.

Evelyn