You don't really expect Crystal to support every data format that comes along do you? IMO, Crystal does things the right way by supporting data access standards rather than every application's proprietary format. Think about your tool. If you were to market it as a generic developer tool, what data formats would you support?

As for integration with VFP, every version of Crystal has gotten better. The integration now is totally seamless. You can now use XML or pass an ADO recordset to the RDC.


>
>Thanks for the response. I have been torn on what to charge but I also don't want to sell myself short. I've been thinking about a VFP Report replacement for over 2 years. I think there would be a lot more developers using VFP today if we hadn't been waiting for an improved VFP Report Writer for the last 7 1/2 Years. As it is now a lot of people have purchased Crystal Reports to get around the VFP Report Writer limitations. I have already spent over $1000 buying Crystal Reports 4, 5 and 8 and haven't shipped it with a single product due to early version crashes to PITA integration with VFP.
>
>I'm not trying to replace Crystal Reports with my tool. But if I can someday then that would be cool. Right now I'm just out to supply an alternative that better integrates with VFP and is very fast. I could always price it like Crystal Reports $595 for Developer's version and then charge $315 for upgrades every year or so and only support FOX2X tables, OLEDB or ODBC. Maybe if I included a copy of my version of the VFP Report Design tool with it, it would entice more sales for the price. But probably not too many people want to see live data in the Report Designer anyway.
>
>I really don't want to disappear as a creator. Was that due to underworld mafia type developers? <g>