>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
Does the NAS support multiuser-locking in databases and Opportunistic Locking? Is it configured to do so?
.·*´¨)
.·`TCH
(..·*
010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"
