This is because the entire command line is parsed at once, before publish.acl has been loaded, and the parser doesn't recognize your function call. You can defer the parsing of your second function by placing "exec" in front of it:
Now Ed let's be nice about this or I'll not buy you a beer in San Antone. 🙂 I mean it is 8.1G. Yes, Epic now incorporates the global features but there may be extenuating circumstances for not upgrading. You want archaic? My old company is still using Adept ( are you ready for this??? Sitting down???)
At least version 8 could say XML and supports the 28001BA1 version of the FOSI.
"Benton, Ed L" <ed.l.benton to:=" "'firstname.lastname@example.org'"=" <email@example.com="> @lmco.com> cc: Sent by: Subject: RE: Start adept from the command line and then execute a function owner-adepters 02/13/2003 12:12 PM Please respond to adepters
Adept 8.1!? Man, get into the 21st century! Anyway, try the exec command in front of your function (i.e. exec