I'm trying to retrofit a fix into an update subroutine called from lots of places, 1 to 3 layers deep, in legacy code. Currently the subr writes many records, releasing each. Sometimes it shouldn't release; it should let the calling program control that. (By the way, stale memory records in calling programs is not an issue in my particular case. Yes, I thought about that.)
This is the reason "nested transactions" were invented. *Sigh* Don't suggest retrofitting UV's transaction logging (START/COMMIT/ABORT). I love it for new systems, but I avoid retrofitting it. All I can think of is to execute "LIST.READU USER [self]" and parse, but I have this vague idea that there is a basic command that I'm not remembering. Thanks, Chuck Stevenson ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
