Thank you, Tracy. I already checked one of the messages you references and it could lead to a solution. My code is very simple (and it works in most other customer settings). It is USE (table) SHARED, that's all. And in some cases, particularly this customer, it fails with the error 108. I will further read on the references you quoted here.

>There could be many things happening. Is the header being locked? Or the database? Do you use transactions? Are you using buffering? Is exclusive off? Are these free tables? You can try something like in the message below and see if it makes a difference and then, if not, proceed from there:
>
>Re: Attempting to lock Thread #1282563 Message #1282736
>
>Also check this:
>
>Re: Error 108: What gives? Thread #1175426 Message #1175580
>
>It would be better if you could post more information on the method you currently use for opening and editing a record in a table.
>
>
>>Hi,
>>
>>A customer says that every so often they get an error message 108 File is in use by another user. I suspect that the server where data reside could be causing the problem. Maybe, another user on another application is attempting to read or write. I don't know. But I was thinking to set a timing loop when USEing (opening) a table to allow for, say, 5 or 10 seconds. Currently, my code simply attempts to open a table once and if it fails, reports a problem.
>>
>>Is it a good design practice to allow some time for a table to be opened?