Larry;
<snip>
You could have a scenario where you can import/export your data items
accross modules within the same (service) program object, but not beyond.
Then, for all data items that need to be exported beyond the service program
object you would create getter sub-procs.
</snip>

You currently have control over the exportation of variable(s) and
procedures contained in service programs. Using binding source you can limit
what is exported from the service program, this includes exported
variable(s). I have used this isolation to allow a "global" service progam
variable to track which "instance" of the service program was last called.
If the current instance and last instance are the same I do not have to
validate the current instance, read file(s) etc... the  procedure can just
run, otherwise the initialize/instantiate procedure will be run first. The
assumption is that the same instance will be used more than once but it is
not necessarily known in which order the procedures will be called. 


Duane Christen



NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named.  Any use, copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via e-mail.




As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.