>>>>What is happening is the mONLINE_2 is giving a VARIABLE mONLINE_2 is not found when they run the SEOD.... from the frmSEOD.ACTIVATE event. Normally, this has never been a problem, and for the life of me, I can't find anywhere in the called programs that would release the mONLINE_2 paramter.
>>>
>>>Over the years I've seen a few cases where one of the parameters would not be passed - say, I pass four, and in the debugger I see that the first one was eaten by a hungry fox, value of 2nd is passed instead, value of 3rd passed instead of 2nd, 4th instead of 3rd, and .f. for 4th.
>>>
>>>Then I'd mess with the code for a while, try to reproduce it, and all of a sudden the error would go away. Then it would reappear in a different project next year, annoy me for a few minutes, rinse, repeat.
>>
>>Yeah, it is probably of that nature, since the paramaters are not being passed nicely to each other's calling code.
>>
>>I will have to rewrite this soon to pass the parameters as they should have been done originally.
>
>One way that I've found puts my mind at ease is to pass one parameter, an object of which the properties are the actual parameters. Start with an empty object, addproperty() as needed, and on the called side, use pemstatus(toParam, "property", 5) to see if it's passed or not, create a default value instead and so on. A bit more work, but more flexible, and I don't really need to remember all of the parameters and in which order they need to be (but still have to know the names of the ones I want to use).

Good idea.

Thanks!