Hi Fabio,

Yes I realise how this works, what I'm trying to do is detect that the connection is in fact busy.

so the remote view is downloading....

the code progresses and attempts to create a piece of sql pass through on the same shared connection.

I need to be able to detect that the connection is busy, but the problem is that when I attempt to test the busyness of the connection via the statement handle of the spt it always returns false when in theory it should be true...

I need to detect this kind of clash over the shared connection because my system uses progressive fetching of the data rows from the remote views.

This is primarily a performance thing, for example if my view has 100,000 records and the user opens a form which requeries the view, I wouldn't want to make the user wait until all 100,000 arrived.

As soon as the first 100 records (fetchcount) are returned control is passed back to the user who can do whatever they want, whilst the records are downloading in the background.

If the user does some thing that would cause another view to be requeried whilst the original view is returning its recordset, I want to be able to detect the fact that the connection is busy.

I can do this with other remote views sharing the connection but sql pass through commands which use the sqlconnect function to get a statement handle onto the shared connection appear not to work correctly...

Many thanks....and any further help would be appreciated...

Bernard