I've experienced this before on NOVELL - is the server Novell?

>Hi Doug,
>That's what we are testing right now. It's at a remote site so we will have to wait a while to determine if it resolves it or not. the computer is a new XP Pro system and quite fast. If that does not fix it then we will test a small wait in there to see if it makes any difference.
>
>>Hi Tracy,
>>
>>What about defining the tag like...
>>

>>USE (ddir+"archeadr") ORDER TAG profile ALIAS arcorg
>>

>>...and if there is a bad error then SET ORDER TO.
>>
>>What processor type and speed is this computer?
>>
>>Regards
>>Doug Johnston
>>
>>
>>
>>>Thanks for the input Doug. We verified write caching was off on ALL machines initially as one of our first troubleshooting steps. I WISH that had resolved it! :o)
>>>
>>>
>>>>Hi Tracy,
>>>>
>>>>I am currently using VFP6 SP5 and have been getting odd random file acces errors when some of my forms have been executing the data environment. In both cases the clients have had XP PRO as a peer server and more often than not the error happens on the computer where the data is residing.
>>>>
>>>>In the last week I have turned off write caching on thre two "server" computers and have not had an error since. If memory serves me correct both these computers running XP are new 2.4Ghz machines.
>>>>
>>>>I think what I am seeing is a new incarnation of the older FPW2.6 fast computer syndrome, probably caused by all the modern caching (VFP,memory,hard drive etc).
>>>>
>>>>Hope this helps.
>>>>
>>>>Regards
>>>>Doug Johnston
>>>>
>>>>
>>>>
>>>>
>>>>>Update: Forgot to mention that the tables all reside on a server and all are Windows XP Professional. None of the other workstations exhibit this error, in fact, when you receive the error if you move to another workstation the same code will run fine. It is in a prg that runs directly from the main menu in the default data session. No forms are even open at this point. The funny thing is that only restarting the SERVER (not the workstation) will free up the file for that workstation once the error occurs. It only happens on ONE workstation and ONLY on that line (after the file is opened and when the index order is set).
>>>>>
>>>>>On one machine only in Windows XP Professional we get a file in use error when an index order tag is set. I can verify that the table is open (only once) on the same machine and this error only happens on a single machine (so far). Everything appears identical to other machines when this error occurs (program trace, data environment, etc.)
>>>>>
>>>>>

>>>>>	WAIT WINDOW "Searching Receipts..." NOWAIT
>>>>>	SELECT 0
>>>>>*--ERROR DOES NOT OCCUR HERE - the file opens fine
>>>>>	USE (ddir+"archeadr") ALIAS arcorg
>>>>>	IF bad_error
>>>>>		=okay("Receipt file is in use.  Please check other workstations.")
>>>>>		IF !EMPTY(dbfarea)
>>>>>			SELECT(dbfarea)
>>>>>		ENDIF
>>>>>		RETURN
>>>>>	ENDIF
>>>>>*--ERROR OCCURS ON NEXT LINE and error is FILE IS IN USE
>>>>>	SET ORDER TO TAG profile
>>>>>	*---Open Transaction File
>>>>>	USE (ddir+"arctrans") ORDER TAG re_link IN SELECT(1) ALIAS arctrorg
>>>>>	SET RELATION TO re_link INTO arctrorg
>>>>>