thus the readFromString

correct..

The table that appears to get the hung lock file most frequently is not indexed, and is a little of 1 MB in size. We think it's happening during a tcursor locate/edit process

so.. others use the table way, but only this user causes the problem? or this user is the most likely to cause the problem?

if the lock file doesn't clear, it means that the OS hasn't released the table file.. or some other file used in the same operation.. if everyone is just doing something that places a "prevent exclusive" lock (view, simple edit, simple query, etc) then it really shouldn't matter.. but if somebody else tries to do something like a changeto or insert query, you're screwed..

if you've done the repair process, and it still happens, try this.. export the data in the table to ascii, make a new table from scratch, import from the ascii.. might not help, but can't hurt..

externally, it's not "minimum bandwidth", it's "uninterupted bandwidth".. a network "burp" can be a disaster for a remote..

also, make sure oplocks and write caching are disabled, local share is true, etc..