× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



How about using binding procedures?

Michael Schutte
Work 614-492-7419
email  michael_schutte@xxxxxxxxxxxx


                                                                           
             Jen Raihala                                                   
             <jen_raihala@yaho                                             
             o.com>                                                     To 
             Sent by:                  Midrange Systems Technical          
             midrange-l-bounce         Discussion                          
             s@xxxxxxxxxxxx            <midrange-l@xxxxxxxxxxxx>           
                                                                        cc 
                                                                           
             04/06/2006 08:41                                      Subject 
             AM                        /copy prototype                     
                                                                           
                                                                           
             Please respond to                                             
             Midrange Systems                                              
                 Technical                                                 
                Discussion                                                 
             <midrange-l@midra                                             
                 nge.com>                                                  
                                                                           
                                                                           




First a very brief description of the issue:

  Last year, the company decided to move to a one-size for all #xx0000pr
/copy standard. For the most part, after resolving the majprity of
glitches, it has worked pretty well.

  A month ago, (partly my fault because I liked the CalcRow for subfile
error marking), the programmer that developed it, at the request of
another programmer who read some of my code and liked the CalcRow too,
moved a copy of the procedure to the new general copy member (and left  it
in the original one since it is in use in a vast majority of their
programs).

  However, my issue now is in the more generally used one, there is a
calendar lookup that I need for a program, and I was instructed  yesterday
to use the older /copy member... which now duplicates the  CalcRow when I
/copy them both.

  So, is there a way to /copy just the calendar lookup procedure into my
program without /copy the whole protoype?

  Thank you in advance,
  JenR


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.