Running DBA Classic under windows 10.
Sometime during the last year some of our DBA files got corrupted. Specifically payroll. Nothing was evident until recently. All payroll and reports ran fine through the end of the year. Prior to the first payroll of the year we have to run the payroll year end routine [PR-O]. Here's where the problem shows up. The year end routine continuously showed the following error '\\MASTER\dbamfg\default\ISPRMSTER.B - 46' . I assume the message popped once for each employee in the file. We couldn't do much about that so we continued on. Printing W2's went well and we did the first payroll of the year. That all went well until an employee showed us his stub this morning. The weekly and quarterly numbers were correct but the year-to-date numbers were wrong. All the weekly, quarterly and year-to-date numbers should have been the same. It appears that the year-to-date numbers were not cleared as part of the year end process. (the result of the error we were getting).
I have no idea how to proceed. I ran the Maintain Database program but that failed with error 'DBIERR unknown DBAMFG'.  I also ran the Check File Integrity program with no errors.  
Where do I go from here?

Just to be safe, make a backup copy and then run UT-C on the ISPRMSTR file to reindex it.  Status 46 is an access denied (which would explain why the YTD was not zeroed out) sometimes caused by a file being in an older Pervasive format being accessed by the newer version.  However that is not likely because you would have been getting errors every time you did payroll.

Status 12 is File not Found.  That can't be right if you can run payroll as the file must exist.

Recovered files 'FILES.B' and 'FILEDES' from a 2014 archive.
Ran UT-C again. It ran clean. When I tried to access an employee in PR-A, all hell broke loose. The was screen only partially filled. It looks like the employee data that was displayed was in the correct spot on the screen, but the form was not displayed at all. Here are the error messages.
1) Violation at address 76F1F583 in module ntd.dll (sp?)  Write of address 00000014. Got this 4 times.
2) Eventually was given the option to exit the employee without saving. We could not exit the review. Continuously  
got the error 'invalid pointer operation'. Had to close DBA through Task Manager.  

We are on a bronze plan which I think only supports updates. How do I open a support incident?

Lynn,
Sorry if I missed your call. We go home at 4:30 west coast time. I don't how that works out for you.
I did a little more digging. It looks like we lost a lot of files a few years ago. We had a ransomware attack and did not pay. Some how we  removed all the files that had the ransomware tag. No .exe files were affected and DBA ran fine so no one said anything. What did happen, which was also not mentioned, was that evo no longer worked. I guess evo was very rarely used. I want to reinstall evo and have our office start emailing invoices. (I did some work on that years ago). This all sounds like a big chore but ...
Office # is 818-240-4840