I'll go you one better on that one: You can (somewhat) integrate a DBC with Windows security by using the SYS(0) function to validate a user versus a free table of permissible users.

Two things here that are relevent -- a "doh!" and a "hmm" :

The "doh!" is that any table you open in BeforeOpenTables has to be a free table (NOT the same DBC) or VFP will go into a loop until it dies because it'll endlessly recurse into the BeforeOpenTables for obvious reasons.

The "hmm" here is that while the VFP 7 docs state that SYS(0) -- login and machine name -- does not work, it does. Whoops.


>The specific Event is the BeforeOpenTable. All you have to do is check for the existence of something like an application object or some other obscure memory variable that is created by the VFP app when it launches. It could also accept a parameter that , if valid, would allow the access to the table. If it does not exist or an invalid parameter is passed, then some rogue outside source is trying to open the table. Just RETURN .F. in your event code to prevent the opening of the table.