Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

number rounding to ###.01

Status
Not open for further replies.
Feb 17, 2004
52
0
0
GB
Hi all

I've just installed Crystal v10 and opened up a report I created in v8.5

In this report I had a formula that converted a numerical field to a name.

ie... if <numericalfield>=3 then "Bobby Brown" else....

etc..

When I converted to v10, this formula stopped working. I put the numerical field into the report and discovered that instead of showing "3" as the value, it was showing "3.01".

What has happened!? Any clues?

The data is from a SQL Server 2000 DB which hasn't been altered at all.

Thanks



Lido
Development & Reporting
UK
 
I seem to recall reading a different post that had a similar problem.

I think that the problem was resolved by changed the databsae driver that was used to connect to SQL Server. Try using the CR provided ODBC driver to connect.

~Brian
 
I meant to say that you want to use the CR provided SQL Server ODBC driver.

~Brian
 
Sorry about replying so late. I've been in hospital!

Where can I find the CR provided SQL Server ODBC Driver? I'm still struggling with this.

Lido
Development & Reporting
UK
 
Lido

What is the value in the database ? is it 3 or is it 3.01 ?

why not try int(<numericalfield>) = 3

HTH

Gary Parker
MIS Data Analyst
Manchester, England
 
The value in the database is 3.00 and v8.5 had no problem showing this value correctly.

I was hoping I could run the reports in v10 without having to change any formulas. But maybe that isn't the case.

Lido
Development & Reporting
UK
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top