Hi Francis,

Can post your SP code so that I try it out.  Also what are doing with SET 
NOCOUNT.  From memory, if this is OFF you get the amount of affected rows 
returned as well as any result set.  When you then try and move through 
the ADO recordset you therefore don't have any records in it - at least 
not in the first recordset - and you have move to the next recordset in 
the ADO Command object to find the resultset you were expecting back from 
the SQLOLEDB provider

I imagine that you know all of the above already, but just in case...

a: