From: ibisnestremovespambit@iinet.net.au   
      
   Tom Krieg wrote:   
   > Robert,   
   >   
   > Have you looked at ExecMethod()? You can pass a dynarray of data,   
   > including the method name and the library name, to a common method in a   
   > library. This common method then opens the appropriate library, passes   
   > the dynarray of data to that library and calls ExecMethod using the   
   > passed method name. It then returns an answer dynarray containing error   
   > status, error messages and any data or table names to be returned. This   
   > way, any forms only call a single, common method, something like:   
   >   
   > HandleMethod(var dynRequest dyAny, var dynResponse dyAny) where dyAny =   
   > dynarray[] anytype.   
   >   
   > This has been discussed at length a few years ago (can't remember where)   
   > and is a variation on the "Hercules" example.   
   >   
   > Any form, any library, any method to be called. A single (common) method   
   > in the uses clause.   
   >   
   > Robert Molyneux wrote:   
   >>   
   >> I found using the long form was a pain, in that if you change the   
   >> parameters for a method, you have to chase down all the objects that   
   >> use the method. Have you found some problem with the short form?   
   >>   
   >   
   >   
   Yes - now use it a lot, but I also have lots of methods that use   
   specific lists of parameters.   
      
   I think the key is to use a dynarray for parameters - so you can add   
   addition parameters as required without changing the method call,   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)