Implied Decimal Point

  • Thread starter Thread starter The Dow
  • Start date Start date
T

The Dow

Is there an easy way to handle implied decimal points? I have a field with
10 places, 8 before the decimal, 2 after. (e.g 123456890 = 12,345,678.90).
I need to convert this field (and 40 or so like it) to decimal form. I could
set up a formula to divide by 100 for each field, but there's got to be an
easier, less time-consuming way to do it. Any ideas?
 
I am having trouble picturing 40 or so numeric fields. This doesn't sound too
normalized to me.

However, dividing by 100 is as good of solution as any (other than possibly
normalizing).
 
Clearly, you've never worked on a 401(k) plan.... :)

We get a data feed from the client with over 100 fields, where pay and
investments are broken down into numerous categories. It's a raw data feed
and our mainframe system (which no longer exists) used to be able to handle
implied decimal points.

Now we're in Access (because the file's too large for Excel) and trying to
convert the numbers. It just seems like there should be a way to tell Access
that you're reading in implied decimal points instead of having to divide
each field by 100.
 
IMHO, if you are importing numbers that you want to divide by 100 then run an
update query on the import to perform the division.

I have seen a number of former main frame apps that have way too many fields.
 
Back
Top