---

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

---

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

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

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.