>Hmmm... What about a config file instead?
>
>The main advantage is a cleaner interface. As in a parameter object, in a config file you normally has an explicit list of parameters like:
>
>Server=QWERTY
>Dabatase=ABC
>Connection=IP
>Etc=123
>
>Even if you need to make some entry parameters variable (i.e. the content of a config variable or the resutl of a batch file), this is usually limited to a few parameters, while most of them belong to a config file.
>
>Again, I don't know your case, so maybe this is not an option.

In some cases, it might apply. In our case, multiple developers will launch the EXE with custom parameters. So, the same EXE on the same PC can be used by multiple developers occasionnaly and they will all have their own preferences depending on which PRG they wish to execute with the choice of multiple parameters. Basically, the request was to have an EXE as a wrapper to multiple very small PRG to be executed without the need to have them compiled and framed within a framework to log and collect data.