That is true, but you have to have VFP to do this. IMO, there will never be DBC security like you have in SQL Server or Oracle. If you need that kind of security, then you should use those backends instead of VFP tables.

>Hello...
>
>Try it:
>USE dbcname.DBC Exclusiv
>BROWSE
>
>You can find a field with some instructions about your code... Then, erased it and close the table...
>If you open your table, VFP 7 will show you a message, and you can choice to make your table free...
>
>After this, your DBF is free for use...
>
>I think it's not security itself... You can lock it with Windows NT / 2000...
>
>Sorry about my English! :) I'm from Brazil!
>
>Rodolfo Duarte
>
>>>Hi! is there any one who can tell me in short that whats the major difference between VFP6 & VFP7 is Microsoft provided some login security on database or not ?
>>
>>http://msdn.microsoft.com/vfoxpro/prodinfo/new.asp
>>
>>There are new database events for the DBC where you can customize and restrict access to your tables. Specifically there is a BeforeOpenTable where you can place code to check for the existence of a global app object created by your application when it is launched. If the object does not exist, just return false, and the table is not opened. This prevents users from bypassing your app and using MS Access or some other tool to access your VFP data.