>>
>>PMFJI. We've been bitten by this a number of times. Cursors client side don't always behave properly. I'm not clear as to what are the differences between the two and when you would want to do one vs. the other.

>Well, if you want to go distributed you have no choice but to go with disconnected client side recordsets. That or concoct a solution of your own.

We've used both client and server side cursors with success. You just use the record set in your asp page to display a table or perhaps a pick list. The client doesn't need to directly access the cursor.

But unfortunatlely, you also lose things like the recordcount, which can be a PITA.