>Jim, I use VMF rather than MM framework, but there is a difference between 'modifiying' and 'adding to'. In this case, Mat is going to HAVE to have an LParameter statement and code to handle the parameters in his MAIN program. Surely this can be done without disturbing the MM functionality? I know in VMF we are encouraged to make our own MAIN program and call their 'initial' prg from our code.
>
>HTH
>Barbara

Barbara and Ed,

Again thanks for your suggestions, but this is really a Mere Mortals specific question. Like I mentioned earlier, I understand the LPARAMETERS command and how it has to be the first line in the main program in order to accept command line parameters. I have done this in past applications.

The question I am asking is very specific to the framework and my interpretation or misinterpretation of a feature. Here is the paragraph from the developer's guide:

Passing Parameters to the Application
You can pass parameters to an application when running a compiled .exe or .app file from Windows or DOS. If you pass a parameter, its value is stored temporarily in a public variable called guParameter. You can access the value of guParameter during the application startup process, but you need to do so before startup has completed since the guParameter variable is released in Setup.prg after the application object has instantiated. For example, you may want to access guParameter from the application object’s PreInitHook.

There is an LPARAMETERS guParameter command in the setup.prg that is supposed to handle this, I believe. The framework and documentation are very well written. Usually when I run into a problem, the solution already exists, I just need to understand the implementation. I think that is the case here. Maybe someone else using the framework can clarify this. Like Jim said, I should not modify these .prg's since they are core to the framework (also would create an upgrade problem). It is not that Oakleaf does not encourage you to modify the framework to fit your needs, it just that there is a right a wrong place to do it.

Kind Regards,

Mat

By the way, thank you Ed for your many posts regarding the C0000005 error and using setup.exe with Install Shield. In searching the knowledge base here, I have found your messages on both subjects extremely helpful.