John,

It's true anyone who have SysAdmin rights on an SQL Server database can Drop/Alter any tables. It's up to the DBA or the developer to properly set the security. And the same is true for VFP Tables.

That wasn't my point. My point was: Assuming the security was set properly, a user use an application accessing VFP tables and "kill" his workstation in the middle of a write operation, it is likely the DBC or the table or the index will become corrupted. It wasn't intentionnal but it can and does happend.

This does not append with a good server DB such as DB2, Oracle, Sql Server, etc... However, I have seen DB corruption on server DB but it was due to poor server hardware, lack of a good UPS on the server but never caused by a client.

IMHO, data protection against corruption and user errors is also part of security.

>Stephane,
>
>There are questions that I have regarding the interactive access to SQL Server. Many people have MS Access installed on their computer. If a user has access to the SQL Server database, what prevents him/her from just opening an Access Data Project, connecting to the database and editing it interactively? If security hasn't been properly configured, what prevents the user from altering or dropping tables?
>
>John