Now I only wish that I could go to Aruba! *G* Just glad you got it resolved. :o)



>I marked you message as the solution, because it was in fact the right solution from the beginning, even though it hasn't been implemented at once.
>
>I will let the client know that you should receive free cinemas tickets when you are on vacation in Aruba (including a large coke and popcorn)!
>
>>Verify the Novell Server NOS version and Support Pack level.
>>
>>Verify the client settings. For NT/W2K/XP Novell Clients:
>>
>>http://support.novell.com/cgi-bin/search/searchtid.cgi?/10013637.htm
>>
>>For 95/98 Novell Clients:
>>
>>http://support.novell.com/cgi-bin/search/searchtid.cgi?/10013620.htm
>>
>>Verify the following Client settings in the Novell client properties (right click on the red 'N' in the taskbar):
>>
>>use extended file handles = on
>>close behind ticks = 0
>>opportunistic locking = OFF
>>File Caching Enabled=OFF
>>Delay Write =OFF
>>End Of Job =ON
>>Cache Writes = OFF
>>Hold Files = ON
>>True Commit = ON
>>
>>Ensure the MAXIMUM FILE LOCKS PER CONNECTION is set at the server for the number of file locks required by the application and client (raise this number).
>>
>>For a completely Windows network, it is only necessary to set it on the workstation (assuming it is set already on the server) if data is stored on the workstation and that data is accessed by other workstations.
>>
>>For a Novell network, set it on the server if the client uses Novell client software. Setting it on the client is optional but recommended always. If the client is a mixture of Novell and/or MSFT clients then set it on the workstation always also. It is best to use the Novell client fo this very reason. The Novell client is oplock aware, meaning that if file caching is enabled on the workstation then the cache manager is invoked automatically and vice versa. Also keep in mind that OpLocking uses broadcasts and then waits for ACKS.
>>
>>
>>
>>
>>
>>
>>>Hello,
>>>
>>>At one client it happens very frequently that the index of some tables gets corrupted.
>>>
>>>My guess is that the network connection is not very stable, but they checked the connection and say there should be no problems with the network.
>>>
>>>Yesterday a table got corrupted with the message (when appending a record):
>>>

Index file "c:\Cinemas\transactions.cdx" tag "Trusedt" is corrupted. Please rebuild it."

>>>
>>>After that we suggested to run the program locally on the computer. I issued a REINDEX and they worked again. After 20 minutes the same message appeared.
>>>
>>>Then I deleted the CDX file and created the indexes again. That seemed to have helped, but I am not sure what causes this problem.
>>>
>>>The other strange thing is that this program does not alter the field Trusedt.
>>>
>>>Any ideas where I can look for a solution?