> The problem is, that when you pull this number > out of the database, you're typically (depending on the language) going > to be storing it in a floating point type variable...
In this case, it will more likely be a regular string once I pull it out of the db. If I can do the math with native functions _inside_ the database, based on what Len and his link are saying (Thanks Len), I won't have to worry about the arithmetical and storage problems associated with using a float. MPF -- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/ TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc
