I started using the ActiveX control and has several problems. I then switched to Crystal's automation server and all of the problems went away.

As for your error, there are probably some Crystal runtime files that did not get installed/registered correctly on the other computer. Check Crystal's help file for a list of required files.

>I'm in the middle of writing the reports for my app, and I'm using Crystal Reports, mainly for the export options available.
>
>I believe Craig Bernston has provided a few examples of how to incorporate Crystal Reports in a VFP app, one of which was to dump the report data to a fox table, and use that as the data source for the report. Then use the following to instanciate Crystal Reports:
>
>ReportApp = CreateObject("Crystal.CRPE.Application")
>and so on..
>
>This idea worked for me, until I tried to install my app on a different computer. When it came time to run the report, Crystal Reports would tell me that the database (report.dbf file) didn't exist, (even though it did), or FVP would tell me that the "Crystal.CRPE.Application" Class wasn't available.
>
>Looking for other options, I decided to see what it would take to make a report pull data directly from my SQL DB. I added the appropriate SQL tables as data sources for the reports (instead of the temporary FoxPro table mentioned above). The only problem I had now, was issuing the Selection Criteria for the report during runtime.
>I browsed the Component Gallery and found Crystal Report Control, with a "SelectionFormula" property field. I dropped one of these onto my form.
>
>Sorry this is so long-winded, but what my problem boils down to now is that some of my SelectionFormulas work, but some don't. The ones that don't all have date fields in the selection criteria.
>
>My question is, has anyone used the Crystal ActiveX Control? If so, have you experienced anything similar to what I am experiencing now?
>
>Any input would be greatly appreciated!