Numeric strings and toNumber function

[Former Member]

Hello,

I'm having problems with Crystal Reports for Eclipse when using some reports.

The problem comes with reports that contain toNumeric function with a data that is get from the database, it gives an error that says the string is non-numeric even if it is a numeric string. The formula in the reports looks like this:

...
numberVar cantidad_dias := ToNumber({MYVIEW.NumericText});
...

I know that using isNumeric condition it works well, but it works well too when using Crystal Reports 2008 without any condition, so I think it should work for Crystal Reports for Eclipse and return error only in the case that the string isn't numeric. Is it a bug?

Thanks

[Former Member · Accepted solution]

The Log4J tells:

ERROR com.crystaldecisions.reports.saveddata.saveddata.DataView.a(SourceFile:1095) - Failed to evaluate recurring formulas
com.crystaldecisions.reports.formulas.FormulaException$FormulaProgrammingError: Excepción en la fórmula '{@formula1}' en '{MYVIEW.NumericText}':
La cadena es no numérica.
	at ...

It is in spanish, it means: exception in {@formula1} in '{MYVIEW.NumericText}': The string is not numeric.

As I said earlier, this report works fine at Crystal Reports 2008, I think it should work too with CR4E.

Thanks

[Former Member · Accepted solution]

What happens if you have end your formula like so....

.
.
.
numberVar myNum;

myNum := ToNumber({MYVIEW.NumericText});

myNum;

Do you get the same error? It might just have an issue with declaring and assigning and returning everything all at once.

You also mentioned

All the returned values are true, so I think that there's no problem with the database values.
It's strange, because there's no problem if the formula finishes like this:

toNumber({MYVIEW.NumericText})
but the error appears if the formula contains something like this:

numberVar myNum := ToNumber({MYVIEW.NumericText})

Im sure it wont make a difference but you got a lower case toNumber in the working and an uppercase ToNumber in the issue.

But I still think give my initial test a try.

Thanks

Darren

Edited by: Darren Jackson on Oct 29, 2009 3:02 PM

Know this is not a solution to the problem from a CR4E point of view but

If you cant solve the problem in the report, is converting it to a number within the View an option?

[ted_ueda · Accepted solution]

If I can't duplicate the behavior, I can't help you.

And I really do want to duplicate the behavior, and help you.

Something is triggering this, and I don't see the trigger.

Sincerely,

Ted Ueda