Re: Was a decimal point keyed?

We normally make users enter any amount in a character based field.
We have to do so as there are currencies on earth that do not have two decimal
positions.
It also give the liberty to enter any decimal separator they wish for (someone
in the USA will normally enter something else compared with the rest of the
world...)(Just the same as with dates...)..
A simple service program evaluates the string entered and will create an edited
format and the actual numeric value (to be stored).
So someone enters 100 and the currency is USD we will asume this is 100.00 USD
and response that back to the screen.
So someone enters 100 and the currency is JPY (JPY has no decimal positions) we
will assume this is 100 JPY and response that. So 100.8 USD will become 100.80
USD
So 100.89 USD will become 100.89 USD.
So 100.678 USD will become 100678.00 USD (USD has 2 decimal positions so the
entered separator is not validated as such (hence ignored)).

When amounts must be presented we convert the numeric value from the file into
the correct representation for on the screen.
When doing that we take in account the Preference of the Organization or the
Person (present it in *USA or *ISO format).

Kind regards,
Eduard.


________________________________
From: "Wintermute, Sharon" <Sharon.Wintermute@xxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Tue, July 13, 2010 11:09:42 AM
Subject: RE: Was a decimal point keyed?


Did you try to tell them "its like a calculator, you need to tell it
what to do."

They have to key the point on a calculator, why should it be any
different?

Sharon Wintermute

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Timothy Adair
Sent: Tuesday, July 13, 2010 10:05 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Was a decimal point keyed?

Yes, that's correct.  They are used to S/36 type entry (i.e. not keying
the
decimal point).  We're trying to transition them to 2010 but it's a slow

process (think, baby steps).




<rob@xxxxxxxxx> wrote in message
news:mailman.38542.1279032948.2580.midrange-l@xxxxxxxxxxxxxxx

Let me see if I get this right.
Let's pretend you have a 15,5 field.  And if the user keys in
1234567
Then what the number really becomes is 12.34567
And if the user keys in
123.4567
Then, by golly, that is the number.
Is this what you are saying?

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From:  "Timothy Adair" <tadair@xxxxxxxxxxxxxxxx>
To:    midrange-l@xxxxxxxxxxxx
Date:  07/13/2010 10:44 AM
Subject:        Re: Was a decimal point keyed?
Sent by:        midrange-l-bounces@xxxxxxxxxxxx



The simple formula test (if %int(field) = field;) works great to

determine

if they keyed in an explicit decimal point, UNLESS they key in a

decimal

with all trailing zeroes.  IOW, if the number they keyed is an

integer, we

assume they did not key a decimal point.

If they key an integer with a decimal point, then the "test" returns

True,

even though they did actually key an explicit decimal point.

Sorry, I should probably give a little more info.

I'm currently converting a large quantity of old RPG II programs to
free-format RPG IV, and the users want to be able to enter numeric

fields,

with or without keying in a decimal point.  So I have to allow them to
enter
data either way, and determine which way they keyed it in, and display

it

with the decimal point.





"Vern Hamberg" <vhamberg@xxxxxxxxxxx> wrote in message
news:mailman.38512.1279026764.2580.midrange-l@xxxxxxxxxxxxxxx

Tim

Just curious - what does it matter if they type 15.0000? That is
effectively an integer with far too many extra keystroke, that's all

in

one way of looking at it!!

In other words, what does this accomplish?

Vern

On 7/12/2010 1:22 PM, Timothy Adair wrote:

Is there a simple way to determine if a decimal point was explicitly
keyed
in a numeric field?  I've tried about every trick (and combination

of

tricks) that I can think of.

I can do it programmatically by defining the screen field as alpha

and

a

second field as numeric but this gets a bit ugly, and could involve
dozens
of fields in hundreds of programs.

The basic test of ---

      if %int(field) = field;

--- works fine unless the user keys in a value like 15.0000.


Any ideas?

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.