views:

65

answers:

1

I've got an app running in VB6 using Crystal Reports version 9 (shutup -- it's been running great for them for 11 years). I've got MANY crystal reports in this thing, and 99% of them work just fine after our "upgrade" to Windows 7

However, on 1 specific report, when I try to run it from the app, I get the error mentioned above. I've compared it with a report that works fine, and I can't tell any difference whatsoever between them. They use ODBC to connect to SQL Server. They all use the same ODBC DSN.

When I open up Crystal to compare the one that works with the one that doesn't, they look exactly the same! However, if I hit the "lightning bolt" button to preview the report, the one that works just pulls data, the one that doesn't brings up a box pre-filled with all information except for the password, and I have to enter that. Only the first time.

Why is 1 report saving the login credentials, but the 2nd is not?

I've been pulling my hair out for 2 weeks trying to solve this issue on and off.

Please. No matter how silly a suggestion might seem to you, I'm willing to give it a try.

A: 

Silly but who knows...

Is it possible that the report has been built using a different machine where the ODBC driver had a different name?

I recall something from my past when IT had set up ODBC drivers with various names and those clients whose ODBC driver name did not match the one in the report had to sign in the first time they ran it.

G Berdal