I have written a COM DLL (VB6) that has a public method accepting several parameters.

This method returns an ADO recordset.

According to Crystal, I can create a report to utilize this COM component by selecting "COM Connectivity" for a DB connection. I think it early binds the COM component to the CR9 report as it calls this method when I select the COM component from the CR designer.

I have some code in the method to create an ADO recordset and return it to the report.

At this point, everything is fine. I can actually run the report (either against the IDE code or compiled DLL) and it runs fine on my machine.

In production, there is a web server that has RAS installed on it. This will run the report then display it in the CRViewer. The issue is the report fails when run on the server.

It appears that the RAS machine is having problems with the parameters to be passed into the COM component. I can remove the parameters, hard code in some values and the report runs fine in RAS.

Any suggestions?

TIA