|
Hi Marvin, > You are attempting to pass 1 element of the 14a to a procedure that > receives a string that is defined like a procudure (machine address) and > you tack on a Option(*Varsize) just to confuse things even more. When you use LIKE(ProcedureName) the compiler makes the variable the same as that of the return value of the procedure. In Tim's case, it defined the string as "1000A VARYING" Options(*Varsize) made perfect sense to me... he wants to write reusable code that he can run from anywhere. Forcing the size of the parameter to always match seems like it would defeat that to some extent, so he did options(*varsize). Can you please do me a favor when you reply to a digest? Change the topic to match the topic of Tim's message, rather than the topic of the entire digest. That will not only make it easier to keep the messages for a thread together in my inbox and in the archives, but it will also make it more likely that the useful info from your messages will show up properly when someone searches the archives for answers. Thanks!
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.