Re: Storing Numeric Values in the Database

I've got away from DSPPFM almost completely - once in a while the F10/F11 hex over/under is useful.

Instead, I use RUNQRY - it, also, is always there, and it displays everything as their value, not their hex representation. As an example -

runqry () qiws/qcustcdt

You have to put in the empty parentheses - that is where a query name would go.

Or, if you don't like emptiness, try this -

runqry qryfile(qiws/qcustcdt)

If you DO have Query/400 or Query for i installed, you can also get record selection, but you do NOT have to have those products on your system.

HTH
Vern - who likes to find good new uses for technology that's been around awhile!

On 9/2/2011 7:42 AM, Joe Pluta wrote:

On 9/2/2011 7:16 AM, Charles Wilt wrote:

Joe,

My vote is integers for numbers with zero decimal places, otherwise packed.

Couldn't tell you the last time I used DSPPFM to look at a record. I
used SQL or DBU when I need to look at data.

Charles

DSPPFM has its advantages - it's always there, and it quickly shows you
the last record in the file. DBU is close, but you do have to remember
to hit RRN on keyed physicals. But the primary annoyance with packed
fields is when trying to do SQL selects on the JOESD field of an ad hoc
journal dump. It's doable, but just not as easy.

Note that I'm not arguing FOR zoned fields, just seeing if others have
the same issues I do when dealing with packed data.

Joe