Hi craig,

>- No tables hanging around on disk that I need to clean up.

Can be handled in classes, but ok it does seem to be a more clean method.

>- Easier to move the application to SQL Server

I don't quite understand. Why is it easier ? You mean that the CR report can bypass VFP to get its data ? If VFP is still somewhere in the report process I don't see the advantage.

>- Crystal can handle the entire reporting process including data selection

You mean via SQL statements ? If only filtering, you can use the filter in CR.

>- I use ADO throughout the application... makes business objects easier to use

Seems a rather subjective statement. I never use ADO and don't see where I should use ADO other than in Heterogenous n-tier environments where one of the tiers depend on ADO.

>- MS recommends it

Well, to me that is more and more reason to be suspicious ;-). Seriously, it does not seem a legimate reason to me.

>- There is a bug with Crystal's xBase driver that causes memo fields in the report footer to not be printed under certain conditions. I reported this bug to Crystal Decisions and they have confirmed it.

Hmmm.. I never noticed this. However I'll keep this in mind.


Thanks,
Walter,


>>Hi Graig,
>>
>>Not having tried OLE DB yet, why do you prefer OLE DB above Fox2X tables. What are the differences ?
>>
>>Walter,
>>
>>