Has anyone run into this issue after a DAT file has been found to be corrupted (I/O Error) when using RDA with the current version and build?
The standard fix is to delete the company folder entirely from the standard path, and restore from a previous backup. When this is done, transactions entered after the backup are present in the data set. In other words, on Tuesday we restore into a non-existent company folder using Friday's back up and when we immediately run an Audit Trail Report, transactions from Monday and Tuesday are in Sage. Not all the transactions from Monday and Tuesday, just some of the transactions.
Tech Support is unable to explain and unwilling to investigate this issue. Our concern is our VENDOR.DAT file is continually being corrupted, causing the need to restore and re-enter transactions. And some of the transactions that come through after the restore, entered after the back up date, are vendor related. Therefore, we do not know if these particular vendor related transactions are causing the file corruption later. Let alone how they appeared since they were entered after the back up.
If you have not had this experience, thank you for your time and keep this in your mind the next time you restore. If you believe a time machine has been discovered, Tech Support already offered that as an explanation.
