I'm getting the above error using the Native SQL Driver in CR v8 each and every time I have memo fields that have nulls in this report.
If I remove the fields every thing is fine(if you can call it that)
So I switched to an ODBC driver and what do you know?
The report runs each and every time with my memo fields and nulls.
Is this a bug that CR and you experts are aware of or should I call CR?
Are there any other support/performance drawback of using a ODBC driver. I plan on distrbuting a FileDSN with the product.
Thanks for your input.
If I remove the fields every thing is fine(if you can call it that)
So I switched to an ODBC driver and what do you know?
The report runs each and every time with my memo fields and nulls.
Is this a bug that CR and you experts are aware of or should I call CR?
Are there any other support/performance drawback of using a ODBC driver. I plan on distrbuting a FileDSN with the product.
Thanks for your input.