>>Yes, you have to declare as much parameters as the maximum expected, but you can know the actual number of parameters passed by using pCount(). Checking for the first logical FALSE could be misleading because it could be a valid parameter.
>
>Yes, I would do like that.
>
>>Furthermore, if this is something beyond your control, you don't have other choice. If you can control the caller side, a better idea can be refactor this solution by introducing a parameter object, or maybe you already have an object with this data, and then you can pass it trough.
>
>This can't be as this is the EXE entry parameters. This is launch from an icon.

Michele,

Another idea would be to launch the exe with only one parameter, which it would be a comma separated list of parameters, then in your main prg you only need one receiving parameter and some code to parse it, something like:

let's say this is your launching icon

some.exe "Some Char Parameter",SomeLogicalParameter,SomeNumericParameter,YouGetTheIdea

Then your main program would receive this list and parse it

lparameters tcParameterList && Unlimited (well almost)

local laParameters(1), lnParameterCount, lnParameter

if vartype(tcParameterList) = 'C'
   lnParameterCount = alines(laParameters, tcParameterList, ',')
else
   lnParameterCount = 0
endif

* Now in the array you have all the parameters, but all as character, so you convert them to their original type:
for lnParameter = 1 to lnParameterCount
    lcParameter   = laParameters[lnParameterCount] && an intermediate value
    if type(lcParameter) = 'U' && The parameter was just a character not between quotes
       laParameters[lnParameterCount] = tcParameter
    else
       laParameters[lnParameterCount] = evaluate(tcParameter)
    endif
endfor

* Now laParameters is an array with all parameters and their respective type

I just wrote the code in here without any testing whatsoever, just to give you a different idea