In regard to your question about the .NET object model: Well, that's something you can't use directly in VFP, VFP isn't a .NET language. West Wind has a VFP .NET bridge for such things, but it varies, whether you can make use of it or not. I only had good experiences with an assembly (C#) DLL I did myself in the .NET framework version West Winds .NET bridge supports and it mainly also is intended to make use of native .NET framework classes. It adds an extra layer to the Assembly interface, a wrapper/adapter if you want to use that to interface to the .NET interface:
I don't know if that causes too many new work in progress spots at the same time. If you want to make use of Crystal Reports because you have Crystal Report knowledge it may be worth to find such a bridging component. I don't know Jeff-Net and googled it. Turns out it is a Crystal Reports scheduler and viewer, so it offers a bit more than ShellExecuting a report file.
The question is, what kind of interfacing do you really need? Crystal Reports, as far as I know, is a self-contained report designer, reports define their input data and output layout and output file type, if not reporting to printers, don't they? They can read DBFs via ODBC driver and possibly OLEDB provider, so such reports only need to be run from your VFP application, wouldn't they? Everything else could be done within the Crystal Reports application and designers totally independent from VFP. Wouldn't that suffice already?
If you are not familiar with any reporting engine, perhaps you should rather look into MSSQL Reporting Services. VFP can interface with SQL Server easily, most obviously as a remote database, which will become the data source for reporting services. You can start experimenting with the Express version and also have much more than just reporting, it's worth combining any VFP application with MSSQL backend, as that can be a basis for many other technologies capable of using the data from there. Crystal also integrates with MSSQL, for example, so while it's certainly not the main nature of MSSQL, it can bridge VFP and Crystal, too, if I'm not having a totally wrong idea about Crystal.
Bye, Olaf.