In the current AC GDL, the method of passing parameters between Macros makes it unsuitable for using GDL in a large scale project. At the moment, the current AC GDL only allows parameters to be passed into a macro and not out of a macro. Well, you can argue that this is not quite true because you can somehow get around this problem by using put command in one macro and a get command in another or you can even argue that there are twenty Global user variable you can use to tackle that. Well, for the put and get method, this would only work for a number but not string and it makes passing of arrays between macros quite clumsy. For the Global parameters method, the first obvious problem is its limit of twenty parameters. The biggest problem though is the fact that you can't define Global parameters as an array. That would render this global parameters to be almost useless for some big scale projects. Obviously, you can still say that one can create some temporary database just for passing parameters between macro but this method is very inefficient for large scale project. Is it possible to make the call process like:

CALL object_name PARAMETERS_IN hit=hit,dep=dep,etc.
     & nbsp;    PARAMETERS_OUT cost=cost,no_stud=no_stud

--
Webscape Team
Alfred Man

webscape.com