>>>>>>>
Is there a property in VFP 9 database (or a VFP setting) that would make all tables of the database to be read only?>>>>>>>
>>>>>>>What is it that you are trying to accomplish here?
>>>>>>
>>>>>>I have some customers that I am converting to SQL Server database (from VFP). The VFP database and tables are still on their drive and could theoretically be accessible. I would like to prevent it without actually deleting the VFP database.
>>>>>
>>>>>As Sergei suggested - set the files to readonly.
>>>>
>>>>If this is the only choice, this is what I will do.
>>>
>>>Basically, they can easily remove the ReadOnly attrribute through Windows Explorer. If they can change the tables outside of your application, there is nothing that you can do.
>>
>>True. I am thinking that if I could create a trigger in the VFP database that would create a record in some "audit" table of the VFP database whenever any new record is added to any table, it would be help me to prevent a problem.
>
>I don't think it's possible with one generic trigger - the trigger needs to be on every single table. Of course, you may generate code to add such trigger to each table.
That would be too much. Eventually I will "remove" the VFP database out of the "reach" of the user anyway. I am just exploring different scenarios for the short term.
"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