Crystal Reports Assumes Wrong Datatype Of Column From Stored Proc

What can be the reason that Crystal Reports Engine sometimes thinks that a field, that is returned from some stored procedure, that is in fact is of type money, is a varchar 255? B

Solution 1:

Are you sure you have the field cast as money? Did you change the datatype recently, and not select Verify Database in Crystal Reports afterwards? If so, it could just be Crystal Reports being difficult; I've seen it do strange things from time to time with no real expalantion why.

That said, you could always create a Formula Field that contains:

ToNumber({YourTable.YourField})

You can then show this formula field on your report, and apply number formatting to the field. I know it's not the best answer, but it's a viable workaround.