>Why change? Stupid reason, sales rep says it MIGHT sell better if reports are in Crystal! I've been posponing it as you can well understand. I'm still not sure I'll do it. I just took this opportunity to get a feeling of how it could be done.

You should try to get some concrete reasons behind it rather than a "MIGHT sell better". IMO, you're open to failure and negative ROI. Maybe a good book on Six Sigma may help people understand the importance of data to back up a decision. Especially one with as much work as this one has.

Before looking at rewriting reports, IMO, you should wait until VFP 9.0 and evaluate the new reporting features there. I can tell you that reports will look better and you'll have lots more capabilities with almost no code/report changes.


>
>You know what Craig, I'm still not clear on how you would do it. Would it be something like this:
>
>Step 1: open the frx and modify to do COPY TO .. TYPE FOX2X then run the frx to creates the table automatically.
>
>Step 2: open Crystal, choose the new table created in step1 as my data source.
>
>Step 3: Drop fields and caption in Crystal and design the reports with conditions, totals, etc.
>
>Step 4 : Keep the table creates in Step 1 just in case I need it again. Or maybe that is not necessary?
>
>My small experience is with Crystal 8.5

You won't be able to do anything with the current FRX. Here's the process:

1. Create the data cursors necessary for the report. COPY TO .. TYPE FOX2X.
2. Open the report in VFP Report Designer.
3. Open Crystal and set the data sources to the FOX2X tables.
4. Create the report in Crystal so that it mimics the VFP report.


You'll also need to do some coding to integrate the Crystal Runtime into your application. But, this can be classes that generically handle the printing/previewing of the reports.