Hi Michel,

I've just read through the thread to date. The problem does seem to be that you are somehow (*sometimes*) using a connection referenced at the global level (given that you have no shared properties).

And if that is true then it is possible that Steven's suggestion as to the cause of the SQL errors is valid - if when you open a connection you then set the environment another hit that references the same connection might use it before that setup is complete.

Are the connections always created by your oProcess object? Are there *any* references to connections held in or referenced from oApp?

As a debug exercise you might add a GUID property to your connection class and log this before some of the offending error lines. This should enable you to check whether different hits were actually accessing the same connection and, if so, might also provide a clue as to where this was happening...?

HTH,
Viv






>> Is it concerned to case-sensitivity of SQL collate?
>
>The code is already as is as per the SQL syntax. And, if it would be the case, this means the SQL commands, where that would apply, would not run at all. In my case, it works until a simultaneous hit occurs.