pdoxusrs.lck problem

[m***@gmail.com]

I am running Paradox 10 with Windows 2000 Pro clients. I can open a
table on the network from one machine, but no other user can then access
the table. They get a directory lock (pdoxusrs.lck). Once I close the
table another user can then access it. Help would be appreciated.

Logic that I figured out:
Paradox creates a "pdoxusrs.lck" the moment anyone opens a folder. So, technically if the file exists it means another user is accessing the table. So,
1. For NETWORK SHARED DATA USERS: I guess Setup of BDE Administrator would help .. (I did not implement this)
2. For LOCAL USERS OR USERS WHO CAN CREATE COPY OF DATA : Simply deletion of the pdoxusrs.lck (from the location mentioned in the messagebox) works ... (It just worked for me as I created a copy of the data folder and deleted the pdoxusrs.lck file)

[m***@gmail.com]

I am running Paradox 10 with Windows 2000 Pro clients. I can open a
table on the network from one machine, but no other user can then access
the table. They get a directory lock (pdoxusrs.lck). Once I close the
table another user can then access it. Help would be appreciated.

Logic that I figured out:
Paradox creates a "pdoxusrs.lck" the moment anyone opens a Table. So, technically if the file exists it means another user is accessing the table. So,
1. For NETWORK SHARED DATA USERS: I guess Setup of BDE Administrator would help .. (I did not implement this)
2. For LOCAL USERS OR USERS WHO CAN CREATE COPY OF DATA : Simply deletion of the pdoxusrs.lck (from the location mentioned in the messagebox) works ... (It just worked for me as I created a copy of the data folder and deleted the pdoxusrs.lck file)

[m***@gmail.com]

I am running Paradox 10 with Windows 2000 Pro clients. I can open a
table on the network from one machine, but no other user can then access
the table. They get a directory lock (pdoxusrs.lck). Once I close the
table another user can then access it. Help would be appreciated.

Logic that I figured out:
Paradox creates a "pdoxusrs.lck" the moment anyone opens a table. So, technically if the file exists it means another user is accessing the table. So,
1. For NETWORK SHARED DATA USERS: I guess Setup of BDE Administrator would help .. (I did not implement this)
2. For LOCAL USERS OR USERS WHO CAN CREATE COPY OF DATA : Simply deletion of the pdoxusrs.lck (from the location mentioned in the messagebox) works ... (It just worked for me as I created a copy of the data folder and deleted the pdoxusrs.lck file)