Crystal 2016 doesn't use local regional settings to display Currency.

[former_member1327248]

I am running Crystal 2016 SP3, I have converted some financial reports from Version 7.

My windows local settings are set to Ireland as per the right hand side of my screen shot, but the left hand side you can see the crystal report it is displaying £ signs. The previous version of Crystal picks the currency based on the regional settings on the local machine.

I have put the Content & Selection locale formulas on both of these are defaulting to en_GB even though my PC settings are en_IE.

In my database the fields are money/currency fields but when you look at them via Crystal they display as number fields.

Is these any other reason why they might not be displaying the currency symbol correctly?

[former_member11696]

CR connects to the ODBC driver, queries it for info about the database and copies it into the RPT file. Info includes what the CLient is telling CR what the field types are. In this case even though it's a currency field CR is being told/or it is mapping that field type as a number.

CR 7 is based on 20 year old technology and connection info for that time era.

CR 2016 uses newer references and database connection properties and all of the database connection and query builder were removed from the main engine and pushed into separate dll's. We basically removed all of the DB hacks we had to add to fix Client issues.

Comparing CR 7 to CR 2016 is not valid, two completely different beasts...

Just saying it worked in CR 7 doesn't prove or provide any info in debugging the issue.

Running those tests will determine if it's the Client returning the Field type into CR as a number or Currency field.

let me know what ODBC and OLEDB tests show the field type as.

Don

[former_member11696]

Technically we don't support 2016 and CR 7 on the same PC. Because CR 7 installs into \windows\system32 folder and those dll's can cause newer version issues.

In Help About... more info button do you see p2*syb*.dll being loaded or p2sodbc.dll? Or something like that?

So what is likely happening is the Sybase driver is not capable or CR does not support Currency field types, that is either CRD needs to be updated or the Sybase Client needs an update.

If you run a query in Sybase to get the DB/Table info how does it return the field description. Try it in ODBCTest and OLE DBTest, they are tools on Microsoft's site and see how the field types are returned.

Run the Crystal query also and see if it returns the vlaues.

Don

[former_member1327248]

Hi Don,

the issue isn't within CR7 & 2016, ironically that works perfect.

If you re read the issue it is within CR16 & 2016. It is since our upgrade / migration to CR16 that we have now had this issue.

[former_member1327248]

Hi Don,

In both 2016 & 7 the same field displays as a number field. In the database it is a money field, but even so in 7 it displays the correct currency who your regional settings are set relative.

[former_member11696]

Did you try changing the field properties?

If CR 2016 doesn't recognize it as a currency field it may be an issue with the DB client.

If you right click on the field in CR 7 does it show it as a currency field?

Can you post the field properties, I'll see if I can dup it.

Don

[former_member1327248]

Hi Don,

Have you any further input on my below issue?

[former_member1327248]

Hi Don,

We are using Sybase 16.

The report is returning the field as a Number field even though it is a money / currency field inside the database. As I said in earlier I can run both CRD 16 & 7 side by side, change my region within Windows and CR7 updates the currency straight away where as CR16 does not change at all.

[former_member11696]

Hi Simon,

What database client are you using? Reason I ask is that sometimes the Client is converting the characters which will overwrite the values you selected in CR.

Also, open the report in CRD and right click on the currency field. Click on the Number tab and try setting it to System local and the others to see if that makes any difference.

Don