RE: READC and *INPUT datastructure

How is this different from what you do today? You would use the

subfile
record number to somehow determine the relevant data, right? Or
something
else that will lead you to the right row. I'm missing something,
perhaps?

The subfile RRN is not enough information. I need the key data, which
is
output capable only. Wouldn't want the user changing the key data
anyway.
You did give me an idea though, so I looked at doing a CHAIN after the
READC with the RRN as the key, and guess what, CHAIN also requires a
data
structure defined as *INPUT. So, I still don't know what data the user
is
selecting, unless I use the global fields, which defeats the purpose of
reading into data structures in the first place.

Sorry to belabor this, but again, how is this different from your current
approach? If you give me an example (hopefully just a few lines) of a DSPF
and program that exhibit the issue, maybe it would help. But your issue is
not going to that you need output fields copied into your DS. Your issue
will be that you are designing everything to be output except one non-key
data element.

Really looking forward to seeing how you do this "the old way."

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
The bigger they are, the harder they hit.