RE: Passing a pointer as a parameter.

>and that's why I was trying to avoid a second
>read, 

Granted I'm jumping in late here, but are you doing all this passing
truly just to avoid reading the same row in the table in 2 programs? In
some _extreme_ cases that might be worth it, but if these two reads are
going to occur at nearly the same time, (pgm a reads, does a couple
things, calls pgm b, pgm b reads) then you've got a _really_ good chance
that the row is still in memory so the "read" isn't going to cost much
at all. 

Sure, in absolute terms it will be "slower" to do the additional read,
but unless you're doing this on a really undersized box, or doing is
millions of times in a job I doubt you'd ever see the performance
difference -- and if you're doing it a million times it should be in
batch so who cares if the job runs an extra 10 seconds. 

Consider such pathological coupling of programs seriously before you do
it -- you're making is much more difficult to reuse Pgm B since anything
that calls it must now know how it works.

JMTCW.

-Walden


------------
Walden H Leverich III
Tech Software
(516) 627-3800 x11
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)