I have an application that uses remote views. The connection properties is set to pull 100 records per batch.

My main problem is that on large queries the user may try to perform another option while records are still being pulled in the background. This of course generates the connection too busy error. It also seems that the query does not pull all the records unless you scroll down in the grid.

I'd rather not change the connection to pull 'All' at once because it's possible there could be many. I also suppose I could use a seperate connection for the other operations on the form, but I'd like to keep the connection count down if possible.

Anyone got suggestions on the most appropriate way to handle this scenerio.

Greg