>>>>We have been receiving this 1705 error when trying to open a table exclusively and we're trying to track down the problem. This error is not consistent. It occurs once every two weeks.
>>>>
>>>>We are running an exe that does some heavy data processing. Below is an example of the code.
>>>>
>>>>... Heavy data processing ...
>>>>

>>>>
>>>>Flush
>>>>
>>>>Sys(1104)
>>>>
>>>>>>Close Databases All
>>>>
>>>>If Used( < table > )
>>>>    Use In < table >
>>>>EndIf
>>>>
>>>>Use < table > In 0 Exclusive
>>>>
>>>>

>>>>
>>>>This last generates a 1705 error.
>>>>
>>>>File access is denied (Error 1705)
>>>>You have attempted to write to a file that is write protected.
>>>>
>>>>We are guessing that after the heavy processing the files have not closed properly, which is why we are getting that error. But why a 1705? Why not a "File is in use." error?
>>>
>>>Have you tried FLUSH ahead of your USE ... EXCLUSIVE?
>>
>>Yes. See there is a FLUSH in the code.
>>
>>:) Before you check the previous messages, I just added that Flush. I should have included that in the first message. Have you actually received a 1705 error when trying to open a table exclusively?
>
>I haven't encountered this error in these circumstances.
>
>If you're going to try a FLUSH to get around a suspected OS file-opening issue, you should issue it as close to the "problem" as possible; in this case, immediately before the USE ... EXCLUSIVE. You might try another SYS(1104) there as well.

I altered the code yesterday to do basically what you said. Ofcourse the error hasn't appeared for three days, so only time will tell if this will resolve the problem.