>>In the beginning, because of the learning curve, that's true, and likely to be true for many tools.

>>However, the development process and performance with .NET/CR can be just as good as with the VFP report writer - not to mention that CR is a more robust and more full-featured report writer than what Fox has (and that's nothing against Fox, the VFP RW is a good one....CR is simply better)

I agree that CR is more robust than the VFP RW.
My real problem has been figuring out how to use it with the variety of data access methods available with C#.
I've been using LINQ-TO-SQL and I love it for the data handling aspects of my app, but I haven't been able to figure out how to hook those object to a CR successfully. I found some things on Google, but they're just too convoluted for my pedestrian mind.
It seems like a cop-out to use CR with ODBC drivers with those nice objects sitting there but that's what I wound up doing.