This is likely due to either a damaged installation of Borland, or data issues.  

Replace Borland completely per Knowledgebase article 13563 initially.  If that does not change anything, try running Data Verification on the database and see if there are any errors that need to be addressed separately.

I tried reinstalling BDE as per an earlier suggestion that I try that article. No change whatsoever. All running data verification does is eat up 40% of your clock cycle forever without ever showing any progress. The answer to the question posed at the beginning of this thread is a definitive "NO," When you get this error message your system is hammered and there is NO FIX.

I tried reinstalling BDE as per an earlier suggestion that I try that article. No change whatsoever. All running data verification does is eat up 40% of your clock cycle forever without ever showing any progress. The answer to the question posed at the beginning of this thread is a definitive "NO," When you get this error message your system is hammered and there is NO FIX.

People in these forums are attempting to help you.  I do hope you will give us an opportunity to do so.  We are professionals, and we do have a great deal of knowledge concerning this program that you may not have.

The Data Verification will pause on tables 47 (Bill Images), 49 (Slip Transactions) and 73 (Audit table) for an extensive period of time as these are the three largest tables.  Running Data Verification should be done on a local copy of the database as well for performance reasons.

How is somebody unfamiliar with the task manager supposed to know that data verification is actually doing anything? How about challenging my assertion that the answer to my original question is "no"? There's no reason why any user should be dealing with the limitations of a DOS database engine that's been obsolete for more than 20 years in this day and age.

If all the suggestions so far haven't helped you have you tried disabling opportunistic locking? Go to Station Administrator > Diagnose This computer > Change Operating System Settings > Untick Enable Opportunistic Locking > Click OK and exit.
You may find that you will have to restart the computer for this change to take effect.

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.