by Rick Lipkin » Tue Aug 25, 2015 5:58 pm
Marco
I have seen the destruction the crypto virus causes and it also hits .mdb ( access ) files. Back when I worked for state gov, I used advantage database server and I created a task that started in the morning before staff got in til just before the server backup started in the evening. That task went through and opened every .dbf I had effectively locking out anyone using the FoxPro interpreter from making any ( back door ) changes to my files, but it would still allow staff to use FoxPro to make queries.
With that said .. I was not worried too much about having ALL my tables opened because Advantage was server based and my servers all had battery backup and ( hopefully ) would never lose power and crash.
I will say this, it is dangerous to have all .dbf's open in a traditional DBfCdx application, just because workstations ( especially in a network environment ) tend to hang or lock up intermittently and wrecking havoc with your indexes.
No good answer here .. On one hand you have potential virus corruption ( for non opened tables ) .. on the other hand you could have index corruption with badly mis-behaving workstations. If it were me, the customer needs to understand they were a victim of their own 'self infliction' and should bear the brunt and your 'paid' services to put their business application back together... and hopefully they kept a decent off-site backup to restore their data from or ... 'shame on them'.
I did not mean to be ugly, Just my 2 cents worth.
Rick Lipkin