>>>...and let me give it a try with this. Suggesting this reshuffle of code:
>>>
>>>

SET ASSERTS ON
>>>use in select("language")
>>>
>>>If !File(xlngfile)
>>>	Return nesne
>>>Endif
>>>
>>>select 0
>>>Use (xlngfile) Alias Language Again Shared //----error occurs at this line
>>>

>>>Also, is it possible that the file is in exclusive use in another datasession? I know that normally that would cause a different error, but we're already long way from normal.
>>
>>my error report code sends me list status and list memo too and seem language really used in this datasession and I don't use private datasession with this application. Because it's a POS application. Every time there is one screen, no windows, every file open as exclusive except this file... :)
>
>OK so what happened with the suggestion to change that alias? Perhaps "language" is something used internally by fox for something. Can you try to call it something else, just to get that off the list of suspects?

I gave up...

I changed my code, I don't open language table every time anymore. Users should have to exit and reopen application when changed their language than...