>>What was the suggested workaround ?
>
>

>Application.Lock()
>oDataAdapter.Fill(oDataSet)
>Application.UnLock()
>

>
>When using that, he mentioned that this would limit the scalability. He found that one can improve the scalability to a great extent by configuring the IIS6 Application Pool, Performance tab property "Maximum number of worker processes" to a number greater than the default of 1, to something between 3 and 6.

direction of the recipe and side effects sound familiar <g>