That would be my opinion. It's possible that the currency fields will be faster in complex calculations. I haven't tested that, but it seems likely. However, unless you're performing a very large number of very complex calculations I would be surprised if you got a noticable benifit. If you will be doing a lot of calculations, you may want to benchmark the differences.
>Thanks for the reply. So, since I know 100% that I don't need to handle numbers anywhere near that size and to better handle and display only 2 decimal places I'm probably better off just using Numeric as in the past?
>
>>The main advantage to the currency type is that it can handle numbers from – 922337203685477.5808 to 922337203685477.5807 using only 8 bytes. This is useful if you need to handle large amounts. The four decimal places can be a pain. If you want to display only two you'll need to deal with input masks on everything.
>>
>>>I'm working on developing an app that has a lot of different monetary calculations and fields. In FoxPro 2.x I always used Numeric and I was going to do the same here when I remembered the Currency type. However, the VFP documentation doesn't give much usefull info regarding this data type, so I would be grateful for some insight as to what the benefits, if any, there are to using Currency instead of Numeric. TIA