Bill,
Forget all what I said. I couldn't get you were after something like SQL server security. As Perry said I don't think they would lend that and many other features of SQL server to VFP.
Best regards
PS: _use_() could be used to "pseudo damage and repair" a table. That way you could make the life harder for out of your app "use" if hackers are exception. ie: A table could have an invisible column.
Cetin
>>If you think this is true then just code your own _use_ method.
>
>What purpose would this serve? The use command would bypass my use method giving me nothing I don't already have.
>
>>If the code doesn't belong to you then there is no event to code.
>
>I don't know what you are trying to say here.?.
>
>>You cannot check my events nor you cant just prevent my reading of the table >if you just prevent my opening it by means of use. I could simply take a copy >or what if I'm a good hacker enough to do an absolute disk read&write to play >with your table.
>
>With an OpenTableEvent at least I could prevent someone from using foxpro to open the table just by issuing a use command. Of course this is not hack proof, but at least I have some control over the casual user just using my data. I'm not asking for hack proof security (IT DOESN'T EXIST!). But one thing that would help would be this event.
>
>Try to use a copy of a table that belongs to a DBC without the DBC. Without breaking the backlink or editing the table header. What if they checked if the OpenTableEvent() = .T. as well. If this was .F. they could not allow you to break the backlink.
