> No, I meant, what are all the values for that field. If you don't have
>a lexical representation of a number, you won't be able to convert it, and
>get the error message you are getting.
That's the thing, they aren't, or crystal reports doesn't see it that
way. Either that, or the binding is incorrect.
I've also seen bindings on crystal reports (in earlier versions) just
get messed up, and map the wrong fields to the wrong bindings. If you
verify the data for the report (or outright change the data source and then
change it back) do you still get this?

Signature
- Nicholas Paldino [.NET/C# MVP]
- mvp@spam.guard.caspershouse.com
> All values are numbers from 0-100
>
>> No, I meant, what are all the values for that field. If you don't
>> have
>>a lexical representation of a number, you won't be able to convert it, and
>>get the error message you are getting.