|
<< Click to Display Table of Contents >> Paradox Locks |
  
|
|
<< Click to Display Table of Contents >> Paradox Locks |
|
Though the Paradox DBMS (Borland or Corel), PdxEditor and other paradox applications, provided proper BDE setting, are completely capable of keeping the same tables open working on different records within the same table.
However, trying to open a table kept open in some other application, not sharing the same Paradox Net-file location, will display error messages like for example this:
Table locked by other user (BDE Admin, System: LocalShare: off [Default])
Table locked by other user (BDE Admin, System: LocalShare: on)
This tells you, that
•First, you have been prevented opening the table biolife.db from the DBDemos database directory.
•Second, the table is opened by the other application via a Paradox Net-file located at
D:\BDE\BDESHARED\
which is probably the default Paradox Net-file location as set by the BDE Administrator from the same PC keeping the table open.
However, it may also indicate the location of an ad hoc per session Paradox Net-file specified by the other application.
•Third, if BDE Admin LocalShare is on (Default is Off), it tells you, that the locking file (PDOXUSRS.LCK) is located at the same target location as the table it self.
First, you should change the Paradox Session Net-file location of your PdxEditor used pointing to the same location as specified by the error dialog shown above.
However, when locked as above, the table will not be accessible for other applications, as long as the table is still kept open in the other application primarily accessing the table.
When both applications are pointing to the same Paradox Net-file location, both applications will again be able to access the table in any order of primarily accessing the table.
It an application primarily accessing a Paradox table on a LAN while pointing to a local Paradox Net-file location (e.g. at C:\BDEshared) as set by the PC's local BDE Administrator, no other applications on other PCs on the LAN will be able to access the same table, as long as it is kept open by the primarily accessing application, as no other PCs will be able to "see" the other PC's local C:-drive location.
To solve this
•A) either each PC accessing Paradox tables on a LAN, must change their default Paradox Net-file location (via the BDE Adminisistrator on each PC) to point to the common data location of the Paradox tables accessed - e.g.:
Net-File Dir = L:\Data\PdxDatabase\
•B) or, if having access to the program code (or to the programmer), better programming design is preferrable, reprogramming the applications to use the Paradox per session Net-file solution (just like the PdxEditor), this way bypassing the inadequate design of many Paradox applications relying solely on the local default fall back Net-file location.
As a standard, paradox applications will delete locking files, when no more needed, hence releasing tables for access.
If the PDOXUSRS.LCK file - for some erroneous cause - persists and not in use, you may delete this lock file, if you are sure no application is actually accessing any files in the database directory (consult your network administrator!).