Pierre, You have two distinct pieces of information - a sum of money and a qualifier of what the money will do. If your data can be separated into fields, you should break your data up into two separate fields - one for money and the other for "base number of units".
Thereafter, find the original programmer and teach him/her the KISS maxim - "Keep It Simple Stupid" ----- Original Message ----- From: "Pierre Abbat" <[EMAIL PROTECTED]> To: "U.S. Metric Association" <[email protected]> Sent: Wednesday, December 14, 2005 2:53 PM Subject: [USMA:35411] Use of M for thousand > I'm going through data files that I'm converting, and one of them uses "M" for > thousand, "C" for hundred, "/M" for per thousand, and "/C" for per hundred. > To me "M" on the end of a number means million, and "C" on the end of a > number means 12 in hex. What should I do about these symbols? > > The proposed standard, which I'm using in the program, uses 0000 for both > "pieces" and "for each", so 000012 means "hundred pieces" and 00000e means > "per hundred". Should these be separated? (The number per hundred is actually > dollars per hundred, but the codes ignore dollars.) > > phma >
