But his problem is with people who know how to access the tables directly from FoxPro, Access, Excel, etc. Changing how his FoxPro App/Exe validates users is not going to solve this. He's looking to protect his data from "back door" users.

That means either encrypting it or changing network privileges to keep the wrong people out. And it probably means encrypting it, because the people he wants out are supposed to be able to get to the data through his program, just not through the "back door".

Right, No Phua? Pardon me for speaking for you.

>Here 'tis ----
>

>USE userlist ORDER username                   && Open the user table
>cName=SUBSTR(SYS(0),AT("#",SYS(0))+2,15)      && Use SYS(0) to get current
>                                              && user network user ID
>IF SEEK(cName,"userlist")                     && If this user is OK
>   RETURN .T.                                 && ...then Return True (OK)
>ELSE
>   RETURN .F.                                 && ...else Return False (Not OK)
>ENDIF
>