Different results for same report when it is run

[denisemathieu]

I have crystal 8.5. i've come across an issue. i have a report that was run in crystal. it was run on different workstations and the data appeared differently from one workstation to the next. so the report was saved with data and emailed to me. i opened the report and saw the preview screen and i could tell the data was wrong because the same qty was appearing for a bunch of items. then i closed the report without saving. and i opened it again from my email. when i looked at the preview screen, the data was now correct. both times i printed it to the printer, also, so not a printer issue. so basically, this report showed up with different data everytime i opened it. it's not an odbc issue because i was just opening the report with the data saved. and it is also not just one report. this happened on another report too. any thoughts?

 

[lovalles]

i have present this issue in multiple languages workstation, or in case you have differents date formats on the computer and is having date field filters on the reports.
In my case i used some workstations working in spanish with the date format DD-MM-YY. and in inglish is MM-DD-YY so i had differents results.
Maybe thats your case?.
Hope this Help

 

[ALAMM]

I had run with this issue about an year ago.
The things i will recommend you are:

1) Make sure the ODBC datasource you have on ur machine points to SAME database as the other machine ( In case you have Development and Production Databases)

2) Check the Version of ODBC datasource you have on your machine and on the other machine.
Crystal do not recommend to use Microsoft ODBC drivers to connect for database.It is better to have ODBC drivers of the database you are using.

3) If you are using Crystal developed Drivers ( ie CR xxx ) then check for version compatability.That is crystal might have approved it to be used for Oracle 7.3 and you might be using for Oracle 8i.

4) The best way is to use the driver provided by the DATABASE. ( ie MS SQL driver if you have MS SQL database ) Also make sure you have correct version drivers.
Some machines may have SQL Server 7.0 client connectivity drivers which works for MS SQL 2000 also but results might vary and it is inconsistent.

5) Basically check for all used DLL's you have on ur machine and the other user's machine.