It does not seem like a case of corruption, but I don't know what it IS.
A client's database went south today while they were using it. About 50 dbf tables. I found about 2/3 of the tables to either do "nothing" when trying to edit a record, or to cause A5 to crash. I was starting to test with a dbf recovery tool, but then found this...
If I remove the table's dictionary, then records can be edited.
If I copy just the dbf & cdx to my development database (and use dictionary in development database) then I can edit records.
If I copy the dictionary files from dev. database to client database (using dbf & cdx from client) then I can't edit records.
I copied the adb and al? files from development to client, still can't edit.
Removed master password. Still can't edit.
For this client I don't use AEX, just copy all dictionaries from development to their folder. So it is puzzling why a client table can be copied to development and work, but it does not work in client folder - even after copied to my development machine.
Some of these tables are lookup tables and have not changed in years. There are also 6 folders on the client's system with the same database app, and all of them developed the same problem at about the same time. Even a test database that had not been open in 6 months had the problem.
So I suspected malware/virus. Malwarebytes and MS Security Essentials have found nothing. So far I don't "think" any other of my development databases have contracted the problem after copying the client database to my machine.
At this point I am stumped.
Bill.
A client's database went south today while they were using it. About 50 dbf tables. I found about 2/3 of the tables to either do "nothing" when trying to edit a record, or to cause A5 to crash. I was starting to test with a dbf recovery tool, but then found this...
If I remove the table's dictionary, then records can be edited.
If I copy just the dbf & cdx to my development database (and use dictionary in development database) then I can edit records.
If I copy the dictionary files from dev. database to client database (using dbf & cdx from client) then I can't edit records.
I copied the adb and al? files from development to client, still can't edit.
Removed master password. Still can't edit.
For this client I don't use AEX, just copy all dictionaries from development to their folder. So it is puzzling why a client table can be copied to development and work, but it does not work in client folder - even after copied to my development machine.
Some of these tables are lookup tables and have not changed in years. There are also 6 folders on the client's system with the same database app, and all of them developed the same problem at about the same time. Even a test database that had not been open in 6 months had the problem.
So I suspected malware/virus. Malwarebytes and MS Security Essentials have found nothing. So far I don't "think" any other of my development databases have contracted the problem after copying the client database to my machine.
At this point I am stumped.
Bill.
Comment