HP3000-L Archives

November 2000, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
JIM McINTOSH <[log in to unmask]>
Reply To:
JIM McINTOSH <[log in to unmask]>
Date:
Thu, 16 Nov 2000 15:32:08 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
Thank you. Thank you. Thank you - not only for pointing me to the
Communicator article, but more importantly, for agitating for the
enhancement!  It really improves an already great product.

Steve Dirickson <[log in to unmask]> wrote in message
news:8uv9qv01d9d@enews2.newsguy.com...
> Last year, as the culmination of a multi-year cooperative effort between
> yours truly (doing the bitching) and HP (doing the work), exactly that
> capability was added to Transact. Your 6.5 (or maybe 6.0?) Communicator
has
> an article that talks about Transact, and specifically about this
> capability, which is identified as "deferred database opening". It allows
> you to either defer the opening of a database until it is actually
accessed
> by the Transact program, or to pass in the base ID of a database opened by
> the calling program for use by the called Transact program.
>
> Steve
>
>
> > I have a need to call a subroutine, written in TRANSACT,
> > which contains
> > databases called out in the SYSTEM statement.  The calling
> > routine is not in
> > TRANSACT.  How can I avoid having the subroutine open the
> > databases each time it is called?
>

ATOM RSS1 RSS2