Hi Colin.

It seems to me that you could do yourself a big favor and go to http://www.hentzenwerke.com/catalog/zcatalog.htm and get yourself a copy of Fundamentals: Building Visual Studio Applications on a Visual FoxPro 6.0 Foundation. Even though it was written for version 6, the principles still apply. I know that when I was moving from Fox 2.x to VFP, it was the predecessor to this book that made the light bulb go on for me.

>>>>>When I start a vfp executable with
>>>>>
>>>>>C:\global\global9.exe
>>>>>
>>>>>I get the following error message but on only one of the machines runnining this exe
>>>>>
>>>>>function argument value type or count is invalid
>>>>>
>>>>>If I click on ignore the exe continues OK
>>>>>
>>>>>How do I get rid of the message
>>>>
>>>>I know folks that would sacrastically answer you should fix the bug?
>>>>
>>>>There is a debug option if you run the exe from IDE. Follow it.
>>>>If not set
>>>>DEBUG
>>>>SUSPEND
>>>>right after LPARAMETERS in your main.prg
>>>>Debug
>>>
>>>
>>>I have never used Lparameters
>>>
>>>Can you five me an example
>>>
>>>If I hear you right
>>>
>>>Lparameters and the rest of the line
>>>debug
>>>suspend
>>>
>>>Where do I put I put it - right at the opening of the startup program?
>>>
>>>Why would it only happen on 1 machine when they are all running the same exe?
>>>
>>>Thanks for your help
>>>
>>>Colin
>>
>>there is PARAMETERS and LPARAMETERS.
>>Parameters declares the parameters as PRIVATE while LPARAMETERS declares them as LOCAL.
>>IOW a parameter declared with PARAMETERS is visible to the code you call from the procedurs / main / whatever.
>>In simple words: Use LPARAMETERS. Allways. If you use PARAMETERS in the idea you are doing LOCAL change your code. Codereference or GoFish will do wonders. (do not rely on coderefernces replace on vcx's. It's faulty by vcx design.)
>>
>>Other exe might have different code? Do you have checked the DLL versions? Does the exe rely on external code visible via PATH?
>>There is a number of nearly n to ask questions.
>>
>>The most simple way is to use the debugger see the point where the problems occur and think about it. Anything else is guesswork.
>>
>>If you have figured out the line that is failing and have no idea why, we can try to give advice on a code snippet.
>
>OK thanks