Unsigned interger from MySQL reported in CR7 as signed

[jamiesadler]

I am currently connecting to a MySQL server which has several fields specified as unsigned integers.
When I display the field in a report (CR7) the field is displayed as a signed value and starts giving me negative numbers.
Is there any way to get Crystal to recognise the values correctly?
At present I have to convert the number by checking for a negative value and doing some maths, but I have loads of fields with of the same type.

 

[kenhamady]

What data type does Crystal see these fields as? (Browse field data to see the data type)
Are you connecting via ODBC? Ken Hamady

http://www.kenhamady.com/

Crystal Reports Training/Consulting and a
Quick Reference Guide to VB/Crystal (including ADO)

 

[jamiesadler]

Crystal sees the data as Type:Number
I am currently using MyODBC to connect to the MySQL database
My colleague has specified a 4 byte unsigned integer in the database
e.g. 2731228448 is reported as -1563738848
which is the signed interpretation.

 

[kenhamady]

If you connect through MS Access to this table, does it have the same problem? This will determine if it is CR or the ODBC. Ken Hamady

http://www.kenhamady.com/

Crystal Reports Training/Consulting and a
Quick Reference Guide to VB/Crystal (including ADO)

 

[jamiesadler]

I get the same problem with MSAccess97.
I have found a message that says that ODBC 2.X does not support unsigned integers.
MySQL(TCX) say they have an ODBC 3.0 driver but as yet can't install it due to a Microsoft Problem.
So it looks like I'm stuffed for the moment...