CAN the maximum number of database files that Timeslips can have open be increased?

I couldn't post my latest bill run, because I got this message:

Timeslips has reached the maximum number of database files that it can

have open in a session.  You can use the Station Administrator utility

that is installed with Timeslips to increase this limit.

Of course, there's nothing in Station Administrator (or BDE Administrator) to increase this limit.  Is the program now permanently useless?

  • 0
    Close Timeslips. CLose any other program that runs BDE (word perfect is one). Clear temp files. Go to control panel > BDE Administrator > Configuration > System > Init Change Maxfilehandles to 256.
    You can also try Diagnose this computer in station administrator.
  • 0 in reply to Caren2
    The maxfilehandles were already set for 256. I increased them to 512. No change in the error message. It's hopeless trying to work with this DOS-vintage database ... when it screws up, you're toast. You'd think they'd at least move up to dBase III.
  • 0 in reply to trevbet
    You might want to uninstall and reinstall BDE. There are instructions available in the Sage Knowledgebase and in previous threads in this forum. Timeslips v2017 is no longer based on Paradox/BDE, it is based on Firebird SQL. If you are interested in upgrading you can reach out to me or one of the other consultants on this forum and we can provide you with pricing options.
  • 0 in reply to Caren2
    I'm quite sure that this is an unrecoverable error, Sage knows it, and directs you to a non-solution just to make it look like it CAN be fixed. Station Administrator has no way of increasing the file handles, and diagnose just gives you a permanently spinning wheel. I'll uninstall and reinstall BDE to prove that there's no solution, but I can't find the article you specified with the site's limited searching capabilities. Could you point me to it?
  • 0 in reply to trevbet
    Don't have time right now to search. If you message me privately, or email me, I can send them to you.
  • 0

    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.

  • 0 in reply to RogerS
    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.
  • 0 in reply to trevbet

    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.

  • 0 in reply to RogerS
    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.
  • 0 in reply to trevbet
    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.