>>You'd only be losing the cursor support. You'd still be able to access VFP tables and views via ODBC or ADO and Fox2X tables natively. Doing: then running the Crystal report is not that big of a deal.
>
>Kindof Mickey Mouse if you ask me... whats a powerful database if you have to go through another product to print your data?

Then, according to your definition, SQL Server is Mickey Mouse.

>
>Delphi used to do this with Report Smith and I always said it sucked, just cause there are two languages to learn (Delphi, and then any scripting in the report writer) two runtimes to install, and then the communication between the them wasn't specatcular. Why not update the report designer to be in step with the rest of the product? And if anything doesn't work right, we have a better chance of getting features added to VFP's report writer by the Fox team than asking Seagate do some stuff for lonely ol' VFP.

I would much rather have the Fox team work on other things: Better view designer, better binding of ADO, enhanced editor, OOP menus, than to do something like the report writer. They won't be able to improve on what CR gives you. The fact is, you can totally integrate CR into your app and the end user will never know. It's no different than interfacing anything other COM component.