Refreshing data in Crystal 8.0

[S3066]

Simple question:

In our previous version of Crystal (6.0, I believe), users, upon initally opening a Crystal report, would only need to hit the refresh icon (lightning bolt), and the ODBC connection would be invoked automatically. "Log On/Off Server," then, was not a necessary step.

Yet, in our new Crystal 8.0, which we recently upgraded to, inconsistency occurs. Users are finding, for a select few reports, just hitting the lightning bolt to refresh works as it did previously with version 6.0. That is, hitting the lightning bolt automatically invokes the logon screen to establish an ODBC connection to the data source.

On the other hand, for the majority of reports opened in Crystal 8.0, just clicking on the lightning bolt at the very get-go does NOT cause the ODBC logon screen to appear for a data source connection. Therefore, for these reports users are forced to "Log On/Off Server" and THEN hit the refresh icon, a two-step procedure they never had to do with 6.0 where the refresh icon did it all.

So, we're a bit confused here because the lightning bolt doesn't seem to be functioning as consistently in 8.0 the same way it did with our previous Crystal 6.0.

Any advice, feedback would be much appreciated!

 

[EarlGray]

The really haven't seen the anomaly before, and we're updating from CR 4.5 and 6.0!

If the ODBC connection is made once in CR, and you go out and open another report using that connection, you won't be forced to log on again... and again...

Are you sing different ODBC conections for the two reports? It would be possible, for example, to have set up two differet Data Sources to the same database, under two different ODBC 'names'. If, for example, you were working off an Oracle DB, you might have created 1 connection using CR's Oracle ODBC driver and called it CROracle. Someone else may have created a connector based on the Oracle native driver and called it OracleConnect. If one report was based on the first ODBC connection and another report based on the second connection, opening the second report AFTER opening the first should cause another 'call' to log-in. If BOTH reports were based on the same connection, opening the second connection should <not> raise a call to the log-in routine.

Hope this helps ECS DataSystems, Inc.

http://www.ecsdata.com

A Crystal Partner

 

[S3066]

I've found my question is difficult to explain in mere words ... It's one of those items better shown.

Nevertheless, to take a final (I promise!), brief stab at describing the question, here goes:

In Crystal version 8, when trying to make an INITIAL (first-time) connection to the ODBC data source, do you find it necessary to use Crystal 8's &quot;Log On/Off Server&quot; menu item before hitting the lightning bolt?

Now in version 8 we've found, for the majority of our reports, using the &quot;Log On/Off Server&quot; menu item is necessary to invoke the INITIAL (first-time) ODBC logon and to prevent the Crystal app from hanging.

Before, with version 6, we wouldn't have to use the &quot;Log On/Off Server&quot; menu item. The lightning bolt would automatically cause the ODBC logon screen to appear for us to log on to our ODBC data source for the first time.

Thanks for your patience and time!

We're getting that result with a few of our reports in Crystal 8, but the majority still hang when we try to use the lightning bolt as a one-step procedure to run the report.