>>>Does the NAS support multiuser-locking in databases and Opportunistic Locking? Is it configured to do so?
>>
>>How can I verify that?
>>Thank you.
>>Bruno
>>
>>
>>
>>>>A client of mine reported a weird problem.
>>>>The scenario:
>>>>- Application and data are located on a mapped drive Z:\ which is a Nas (i.e. 192.168.1.20) accessed by three computers.
>>>>- Data are like: TableMaster.dbf (plus TableMaster.cdx), TableDetail.dbf (plus TableDetail.cdx).
>>>>After an insert, through the applicazion form, data got corrupted like that:
>>>>TableMaster.dbf became 5EFC00K.TMP
>>>>TableDetail.dbf became 5EFC00L.TMP
>>>>While CDXs stayed with the correct name: TableMaster.cdx + TableDetail.cdx.
>>>>To solve, I had to manually rename
>>>>5EFC00K.TMP -> TableMaster.dbf
>>>>5EFC00L.TMP -> TableDetail.dbf
>>>>Besides, overwrite CDXs with empty ones, then reindex.
>>>>The question: which may be the explanation for such a problem?
>>>>How to prevent from occourring again?
>>>>TIA.
>>>>Bruno
>>>
>
>Al answered your question much better than I could have... Thanks Al!
You're welcome :)
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up