Error Message

When one of our timekeepers opens timeslips on her computer she gets the following message:

 

File or directory does not exist.

Area: Table

Code: 109

Address: Exception tBDETableExceptionC in module Timeslip.exe at 0085905F.

Version: 14.0.2.34

Table: General Setting

Record: 0

BDE Code: 11010

 

She can't get into the program at all.

What is the cause and how to fix it?

 

Thanks in advance.


  • dscpa wrote:

    When one of our timekeepers opens timeslips on her computer she gets the following message:

     

    File or directory does not exist.

    Area: Table

    Code: 109

    Address: Exception tBDETableExceptionC in module Timeslip.exe at 0085905F.

    Version: 14.0.2.34

    Table: General Setting

    Record: 0

    BDE Code: 11010

     

    She can't get into the program at all.

    What is the cause and how to fix it?

     

    Thanks in advance.


    Just to confirm, you have more than one user in this database and only this one workstation is having the problem?

     

     

  • we have many users (15 liscences although I'm not sure they are all in use). so far this is the only one with the problem. it and a few others had another problem which i hope i just solved by expanding the amount of files handled in the BDE administrator. this is a new database which was created from another database.

  • dscpa wrote:
    we have many users (15 liscences although I'm not sure they are all in use). so far this is the only one with the problem. it and a few others had another problem which i hope i just solved by expanding the amount of files handled in the BDE administrator. this is a new database which was created from another database.

    That's good, because it means that the problem is likely located on that particular machine.  Try this:  search for and delete any of the folowing files on that machine, and then try to open it.

    Pdoxusrs.lck
    Pdoxusrs.net
    Fulses* folders (delete the entire folder)

    Paradox.lck

     

    That may not work, but we'll start with that.  Write back if it doesn't work.

     

    Nancy Duhon

  • Please try the same steps suggested by Nancy in the prior post and let us know the results.
  • Lately we have been having so many problems with timeslips. we are about to upgrade to 2009. don't know if that will make things worse or better.

    the deleting of the paradox files helped a bit. i can now get into the program. but that computer and one other still have the problem that when they do show slips the program crashes.

    one problem at a time!

  • Have you run data verification with only "look for errors" checked? Does it show any errors? This should be done on the same computer where the database resides.

    There could be a memory conflict with another program on the computers - do you have other programs opened at the same time? 

    There are various things that can be tried but this is a little hard to troubleshoot through a forum. One thing I would try is bringing the database local to one of the computers that is having a problem and see if the problem happens when the database is local. This can help identify a network problem.

    More information on your specific setup is really needed to begin to come up with other ideas.


  • dscpa wrote:

    Lately we have been having so many problems with timeslips. we are about to upgrade to 2009. don't know if that will make things worse or better.

    the deleting of the paradox files helped a bit. i can now get into the program. but that computer and one other still have the problem that when they do show slips the program crashes.

    one problem at a time!


    If they are having problems with show slips, try this.  On their machines, go to Setup, Preferences, Interface tab, and click the button on the bottom part of the window that says "Restore all Windows to Default Sizes and Positions."  Sometimes the Show view gets a bad sort or select value stuck and this seems to clear it.

     

    Hope this helps.  If you think this suggestion was especially helpful, please consider clicking the KUDOS! (yellow) icon in this message.  Thanks.

    Nancy Duhon, Esq.
    Certified Consultant for Timeslips and Amicus Attorney
    Duhon Technology Solutions, LLC
    [email protected]
    404-325-9779
    Providing personalized local and remote online support for Timeslips users for over 15 years. 

  • Copy your database local from the server to the local machine and open the database locally. this error indicates a rights issue on that machine.

     

    if you need to clear your database path go to starts>programs>timeslips>station administrator and go to options>clear DB path.

     

    if the DB opens locally then you have a rights issue with that users login. you can also login as the ADMINISTRATOR account in windows and attempt to open Timeslips with the Database on the server as well.

     

    any time you receive a General Settings Record 0 error its either the MAIN table that is damaged or a rights issue. if copying down yields that same error then its most likely main table corruption. If the error does not occur with the DB copied locally then you confirmed a rights issue with in windows.

     

    Each windows user needs at minimum Power User rights in Windows XP/Server 2003

     

    since you mentioned this only occurs on one or 2 and not all machines on the network this also further suggests a localized rights issue with those specific user/machines.

  • in reply to Nancy Duhon

    Did anyone find a solution to this issue? I am having this problem on 5 stations.

    Had a quick power outage now we are locked out with same message

    File or directory does not exist.

    Area: Table

    Code: 109

    Address: Exception tBDETableExceptionC in module Timeslip.exe at 0085905F.

    Version: 14.0.2.34

    Table: General Setting

    Record: 0

    BDE Code: 11010

  • in reply to attorneykelly

    I would start by rebooting the server and then each workstation.

    Before connecting Timeslips again make sure the workstation can connect to the server. Also check for pdoxusrs.lck, pdoxusrs.net or paradox.lck files on the server or workstation and delete any before trying again.

    If that doesn’t work you probably have database damage and need to restore from a backup or get repair assistance.