You can handle this by setting the view that will fetch progressively to not share its connection or by waiting for the view to complete or by cancelling execution of the view with SQLCANCEL(). You can use SQLGETPROP() with the 'ConnectBusy' parameter to see if a connection is busy. The disadvantage of not sharing the connection is that each connection requires resources on the server (assuming you are using a server database).

>But you set the number of records to fetch for example to 10 and you try requery another view where your connection is sharable, then you will get an error saying that your connection is busy.
>
>How do you overcome this problem?