>As a test, I wondered what would happen if someone with appropriate rights to the directory where SQL server stores its database, for some reason deleted or renamed the .MDF or .LDF "Files" that SQL server uses for storing its data.

Since you don't use a mapped drive to connect to SQL Server, how would anyone other than the DBA or Network administration have any idea where the SQL Server files are located?

>Also, if anyone has MS Access or Excel and knows a userid and password for accessing the database, they can make a connection and still wreck havoc in the database even with SQL server if they are intent to do so.

And they have a user ID and password with DB write rights why? I have no problem with people having UserIDs and P/Ws with READ access to the data with Excel and Access but they won't have update/delete level rights.

>Obviously, it is because I have Admin rights and know the userid and password for the database and where SQL server stores its files, but my point is that it is not impossible to delete or trash any database,

True...

>Just my 2 cents. I think VFP is a great tool for most any data intensive application using SQL server, VFP tables or other database servers.

We agree here. < s >