09-23-2009 08:51 AM
A user had a system error that caused a BSOD. This then caused his ACT! Remote DB to stop working. Looking around the knowledge base tells me that .pad file is damaged because I can open the .rdb file and the dbase will open. When the .rdb file or the .alf are opened it does not create a new. pad file like the knowledge base says it should. If I click the .pad file and it trys to verify the dbase I get the attached error.
Also, the dbase is not listed in the actdiag now. Any ideas on how to get it back in there?
09-23-2009 09:06 AM
This problem just keeps getting wierd. If you open the .rdb file from Act! it will throw up the error also. But if you open it through windows explorer and let the .rdb file open Act! itself everything does fine.