Thanks. I'll try that, but first I've got to solve a problem with station administrator.

Could you please elaborate on "extensive period of time?" I've had it running for almost 24 hrs. The clock time hovers around 40%; the memory consumed was 2.7 Meg at the beginning, and got down to .3 after a couple of hours. But it's remained there ever since. What should I do at this point? Can't the amount of time be estimated from the sizes of the three files?

There would be too many variables (Memory, CPU and speed, etc.) so an estimate isn't something I can offer, no. But this sounds too long regardless. I've never had one take more than 30-45 minutes except in an instance where there was some damage that caused an infinite loop through the file being tested.

What table is it that it is testing? It is very likely that the database will have to be fixed with proprietary tools that with Sage or a data-certified consultant will have to use to work on it for a fee - unless you have a support plan and are on a current version. Timeslips 2015 and 2016 for are the only supported Borland versions currently for purposes of Sage to do in-house data repair.

I have PMed you if you wish to converse further with me on this issue.