Heard of this before. It is some sort of dirty read from the BDE, I think.

Is it timing? Same times?
Check for virus scanner or some sort of virus sweep on the machine.

Check UAC.

Check if ALL users NET file locations are same and the usual lock file sweep.
I know you know this, but same path / URL / Drive letter.
Delete the NET file.

Is it same users / machine PRIV?
Delete the whole PRIV folder and recreate, verify security.


Is it a certain template table? Memo fields?

Rebuild all template tables even if seem OK.



Steve Green <steve@oasistradingpost.com> wrote:
>"not exact read/write  f:\pdoxdata\privtabl\pdoxusrs.lck"
>
>we're getting this error on a simple copy(this that) in two particular 
>places, in the middle of our massive overnight process.. that is a 
>shared folder that holds empty template tables, they get copied to the 
>user's priv
>
>the process that calls this line of code, gets called all day long, by 
>many users.. it's not failing anywhere else.. the lock file itself is 
>coming and going properly, the same tables get copied all the time
>
>
>-- 
>Steven Green
>Myrtle Beach, South Carolina USA
>
>http://www.OasisTradingPost.com
>
>Collectibles and Memorabilia
>Vintage Lego Sets and Parts
>- and Paradox support, too