|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] Remember, - This is case sensitive! - You can 'overload'. Basically, if you have multiple subprocedures with the same name (in different service programs) you can create multiple functions with the same name which vary based on the number and type of parameters. Lot of fun (really). Glad to be of assistance. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin MWalter@hanoverwire.com Sent by: midrange-l-admin@midrange.com 11/27/2002 11:30 AM Please respond to midrange-l To: midrange-l@midrange.com cc: Fax to: Subject: Re: Anyone using the *AFTER *READ Triggers in V5R1/V5R2? Tinkered with it a little more. Seems that the UDF name and the sub-procedure name need to be the same. Is this correct? I was able to create multiple UDFs from multiple sub-procedures in one service program as long as I made the UDF name the same as the sub-procedure name. This is good stuff!! Thanks, Mark Mark Walter Sr. Programmer/Analyst Hanover Wire Cloth a div of CCX, Inc. mwalter@hanoverwire.com http://www.hanoverwire.com 717.637.3795 Ext.3040 /"\ \ / X / \ MWalter@hanoverwire .com To: midrange-l@midrange.com Sent by: cc: midrange-l-admin@mi Subject: Re: Anyone using the *AFTER *READ Triggers in V5R1/V5R2? drange.com 11/27/2002 11:17 AM Please respond to midrange-l I was playing with it and made the procedure, service program, and function the same name (as per Rob's example in the midrange faq) and it worked. How would you do this if you had more than one sub-procedure in your service program? Thanks, Mark Mark Walter Sr. Programmer/Analyst Hanover Wire Cloth a div of CCX, Inc. mwalter@hanoverwire.com http://www.hanoverwire.com 717.637.3795 Ext.3040 /"\ \ / X / \ _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com 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 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.