RE: %dec / target for a numeric operation is too small

What troubles me about this (and I was waiting [not too patiently,
apparently ;)] for someone else to point this out) is: Since testscore is a
15.4 variable, why not bite the bullet and make the %decimal( workscore :
15: 4) too? What is the benefit of the approach being used (aside from the
dubious "two CPU hits for the price of one")?

Yes, it is good to understand what's going on - and here's a hand-clap for
the question. (hip-hip) But that solution just looks to me to be ripe for
the picking. Maybe I'm missing something, though.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Health nuts are going to feel stupid someday, lying in hospitals dying of
nothing."
-- Redd Foxx

The precision and decimal places refer to the decimal number that will
be constructed from the right hand side of the equation. That number
will then be assigned to the left hand variable.

It looks like your input field can be as small as '.0001' and as large
as '99999', so I think you are going to need %dec(wrkscore:9:4).

Sam

On 7/26/2010 10:54 AM, Kirk Yates wrote:

Field wrkscore may have a value like 1 or 10.25 or .1258

d wrkscore s 5a
d testscore s 15s 4

testscore = %dec(wrkscore:4:2);


The target for a numeric operation is too small to hold the result (C

G D

F).
Reply . . .


I've adjusted the field sizes trying to get this to work and still

get

the same error. Any suggestions?