>Craig, and all,
>
>>>That sounds interesting. Is it possible to keep people from opening .dbf files with other applications using Database Events?
>>Yes. Create a public variable in your app, then check for it in the Database Events.
>
>What do you mean by other types of applications? If you mean Works, or some other DBF viewer, I don't think the VFP7 DBF format will be recognized (if its a DBC's table that is).

I haven't tried it yet, but I don't think the ODBC nor the OLE DB provider will allow the tables to be opened if you do something with the DBC Events like security. This, of course, won't stop someone from looking at the table with a text editor, but if you're that concered, SQL Server would be a good idea. You could also use the Crypto API built into Windows. There is a new FFC that ships with VFP7 that lets you get to it.


>
>If you mean other VFP7 applications, you should be able to delete/move/rename the DBC and open up the table just fine since the DBC is where teh events are.

Yes, that's true, but most people won't have enough knowledge to do that.

>
>As for security in VFP8? I woudln't count on it, thats how it goes with file based data.

I agree.

>Thats also why MSDE ships with VFP7/

IMO, not the main reason. MS wants us to move to SQL Server. This is a marketing decision.