HP3000-L Archives

March 1995, Week 4

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:
Ray KINGSBURY <[log in to unmask]>
Reply To:
Ray KINGSBURY <[log in to unmask]>
Date:
Thu, 23 Mar 1995 08:42:00 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (27 lines)
>> Is there a way to retrieve IMAGE's internal data item list ("current"
>> list)?
>
> Why do you want to?  If you are making the calls (which you should be),
> then you already "know" what the current list is.  If you aren't making
> the calls, then what good will the information do you?
 
I'd also like to see a way to retrieve the current list for a dataset.
Sure, we're already making the calls with one list, but there are times
when we'll call a subroutine that accesses the same dataset using a
different list, then, when control returns to the calling procedure,
and the same-list (*) construct is used, DBGET returns the information
from the subroutine's list, not the calling procedure's. It would be
nice if the subroutine could retrieve the current list (if any), then
access the database using it's list, then reset the current list to
the one that was in use at the time of the call.
 
Because this is not currently possible, we seldom use the current-list
feature (usually only for DBUPDATEs, where we know that there have not
been any subprogram calls since the previous DBGET).
 =======================================================================
Raymond Kingsbury                       [log in to unmask]
Sr. Programmer/Analyst
College of the Redwoods - Data Processing          Voice: (707) 445-6778
Eureka, CA. 95501                                  Fax:   (707) 445-6990
 =======================================================================

ATOM RSS1 RSS2