Re: Procedures/Sub-Procedures

[HwaRangRon@xxxxxxx]

In a message dated 11/16/99 3:13:26 PM Pacific Standard Time, 
boothm@earth.goddard.edu writes:

<< But more to the point, once the file was in place I discovered it is 
 awfully handy for storing other values too.  The keys can be anything that 
 is useful to provide the needed flexibility and follow-through.  The 
 problem with the Data Area solution was that it is a one-at-a-time sort of 
 solution.
 
 I'm thinking that making that solution into a procedure has great 
 potential? >>

Booth,
We call that the Defaults file. Does exactly what you are describing. I 
wonder if they were developed separately, or if we have people that have a 
shared background? I think it happens all the time in R & D that like ideas 
are generated/created by different teams, but it's pretty amazing to see it 
in action.

I'll definitely move the access to the defaults file into a procedure as part 
of the new release. We're using it all over in place of data areas.

Ron

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---