>>>You might add another security layer by checking with the DBC-Events that the tables are really read-only.
>>>Again, easily overcome - not existant if not opened via VFP or VFP-ODBC/OLEDB driver.
>>>You might just show a big warning screen in the event if the dbf is not read-only
>>>[and add a email to you with a log of when this happened, under which login]
>>>But if someone just uses a Hex-Editor this wont get triggered.
>>
>>The tables do belong to a database (that is housed with DBC). I am not concerned if a table is being accessed by Hex-Editor or any other way outside of my (VFP) application. I am only concerned that somewhere I didn't leave out code in my application that by accident still opens VFP table(s) instead of getting the data from SQL Server.
>
>For that the dbc-events sound tailor-made...
>Log the alias and the stack, show a big screen and have the logs forwarded.
>
>regards
>
>thomas
I will have to lookup how to do dbc-events; never done that. Thank you for the suggestions.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
