Well, :-) I'm still recovering from my machine crash but I will be investigating some of the issues that JVP mentioned. Technically, I think you are not right, :-) cause the connection is still closed when the connection variable goes out of scope when the function exits. But this is one of the things I will be looking at. The main issue for me at this point is that JVP thinks that due to switches in the commands the cursor was coerced to server side instead of client side. This I want to pin down and correct.

Bill

>You mean.....I was right? :-)
>
>>Sorry for the reply delay, got BSOD on my machine yesterday. JVP listed several issues to consider. We expected a client side recordset which should not need a connection. We also found that by removing the MyConn.Close, the problem went away. ADO is relatively new to me so I'll have to study some of the issues.
>>
>>Bill