>>>My app is made to work with $
>>>
>>>I will have to update it so it can work with $ and also Euro. Any tips so I don't suffer too much on this ;-)
>>>
>>>What is the character for Euro that I can use to replace $?
>>
>>For the data structures, I would suggest an amount field, and a field for the currency. That way, you can easily expand to more currencies later. Ideally, the currency field would be a foreign key to a currency table.
>
>And the exchange rate is a historic information, i.e. needs to be recorded with the transaction, or to be retrieved from another table with rates and dates. Keeping only the current rate in a lookup is not going to work.

Right, I forgot to mention that. - Actually, I was mainly thinking about the "alternative", which I often saw here in Bolivia - programmers tend to use one field for the amount in the country currency ("bolivianos"), and another field for the amount in US-dollars... which makes the system quite inflexible when it comes to adding additional currencies, such as the Euro, yen, etc., the currency of some neighboring countries, or perhaps some future Southamerican currency union. Which they may, or may not, need in the future. Currently, it is customary to use only those two currencies - the country's currency, and "foreign currency" which is slang for US-dollar.