Throwback to the past on this one... I have an old application (D5/BDE) that uses some Paradox tables. I have been having issues with stale locks on these tables preventing the application from working due to "Directory is controlled by another NET file" errors.

-
Throwback to the past on this one... I have an old application (D5/BDE) that uses some Paradox tables. I have been having issues with stale locks on these tables preventing the application from working due to "Directory is controlled by another NET file" errors.

1) Is there any way to tell what workstations have locks registered in the PDOXUSERS.NET file? I've seen a few tools that supposedly dump these, but none are compatible with newer operating systems.
2) Is there any way to forcibly terminate these connections and free up the files for access?

I am working on migrating the data from these old Pdox tables to our newer database, but with the locks, I can't even open them to copy records :( Any help appreciated!

Comments

  1. Richard BaroniunasMarch 21, 2018 at 8:27 AM

    I would have to assume you are using Paradox 4/5 tables ?

    From my experience when you are getting that sort of error, first thing is to check the configuration for each workstation using the BDE and check that they are all network mapped to the same folder.

    Check the Local Share to be true.

    See if there are any LCK lying around on the network and the local workstations accessing the application.

    You will need to get some open source and recompile it. I use to have a software kit that I wrote but i cannot locate it at the moment that did repairs and so on.

    Here are some notes concerning LCK/NET - support.novell.com - 1203264: & .LCK Files

    ReplyDelete
  2. Uwe RaabeMarch 21, 2018 at 9:11 AM

    The path where the BDE looks for the PDOXUSRS.NET can be configured in the IDAPI32.CFG (you probably know that). Unfortunately this IDAPI32.CFG is usually stored in a place where a normal user has no write access. In case UAC virtualization steps in any changes to IDAPI32.CFG are not seen by other users.
    You can specify the location for IDAPI32.CFG in the registry under "HKLM\SOFTWARE\WOWO6432Node\Borland\Database Engine". If not exist add a REG_SZ entry named CONFIGFILE01 and enter the complete path to your IDAPI32.CFG.

    ReplyDelete
  3. shlomo abuisakMarch 22, 2018 at 1:17 AM

    what i did many time just delete PDOXUSERS.NET
    BDE will start it again

    ReplyDelete

Post a Comment