CE 8.5 - database dll error when SQL Server reports added

[pastasalad]

A long-standing (10 months) CE8.5 solution that reports on an Oracle 8i database (native connectivity) was recently updated to include some new reports. The new reports run through a native connection against a SQL Server 2000 database.

The solution, which had been stable throughout its 10 month existence, suddenly started throwing up database .dll error messages. These started when the new SQL Server reports were run, but eventually spread to appear when the original Oracle reports were run as well.

The problem persisted until CE8.5 was re-installed on one of the two servers, at which point all ran OK again.

Has anybody seen this pattern before? Our support people need to know (a) why this happened, and (b) how to avoid it when new reports are added in future.

Thanks

Marc

 

[bdreed35]

We had nothing but problems with the Native SQL Server driver when we tried to use it at my company. Apparently the driver has not been updated at all since Crystal Reports 7. I use ODBC for all my SQL Server report to avoid the issue. OLEDB will work as well.

I haven't encountered any issues with our CE 8.5 deployment. I don't know if the SQL Server Native driver had anything to do with it but I would stay away from it.

~Brian

 

[MJRBIM]

Our rule is...when in doubt use ODBC over the native connections.

I've experienced issues with SQL and Oracle - that went away by using an up-to-date ODBC driver.