Stored procedure returns unpredictable results through OLEDB

Can anybody suggest a reason why a stored procedure would behave differently depending on whether it was executed from Query Analyzer, or from an ASP page via OLEDB?

Identical parameters are used in each case.

Through Query Analyzer the stored procedure returns accurate and complete results every time.

When called from the asp page the stored procedure returns an incomplete number of records, and the number of records returned varies each time you refresh the page.

No error message is displayed in the browser ( so a user would be unaware anything had gone wrong).

I have not used On Error Resume Next.

If anybody can help me I would be most grateful

thanks

Not so easy, remotely. Do you have a utility like the MS Profiler that can "sniff" the SQL commands sent to the server?