>Hey, thanks for volunteering Bonnie. Let us know what you find out. :-)

Wait a minute!!! I was actually trying to be subtle about suggesting that *you* benchmark it. <g>

~~Bonnie



>Hey, thanks for volunteering Bonnie. Let us know what you find out. :-) ...Just kidding. :-) I have historically used Convert(), but since the base function is usually Parse(), I'll probably switch to that when applicable.
>
>Bill
>
>>
>>Possibly. It might be interesting to benchmark it, just for the helluva it.
>>
>>~~Bonnie
>>
>>
>>
>>>
>>>>Bill,
>>>>
>>>>According to the docs for Convert.ToDecimal():
>>>>

>>>>The return value is the result of invoking the Decimal.Parse method
>>>>

>>>>So, you might as well just use the Parse! <g> Actually, it doesn't say, and I don't know, if it compiles to the same IL code or not. If it does, then it really wouldn't matter which you use. If it doesn't, then that would mean that the Convert calls the Parse and that *would* be more inefficient.
>>>>
>>>>~~Bonnie
>>>>
>>>>
>>>>>Hi Bonnie,
>>>>>
>>>>>Do you know of reasons/constraints etc. for choosing Parse() or Convert() in a given scenario?
>>>>>
>>>>>Thanks,
>>>>>Bill
>>>>>
>>>>>>Jerry,
>>>>>>
>>>>>>Look at the Decimal.Parse() method.
>>>>>>
>>>>>>~~Bonnie
>>>>>>
>>>>>>
>>>>>>
>>>>>>>How can I convert a string of "25.50" to a number with the decimals?
>>>>>>>
>>>>>>>Thanks,
>>>>>>>
>>>>>>>Jerry