>I forgot to mention that I got rid of the call to the config.fpw file in the shortcut and Voila! There is no longer a Parameter error!!! I cannot tell if something in the below CONFIG.FPW file caused VFP 9.0 to basically bomb out with the "No Parameter is found" error, but once I got rid of the config.fpw call from the shortcut calling the GEM.EXE program, there was no longer a problem.
>
>Is this a VFP 9.0 BUG??? Has anyone else had this same problem?
>
>

>CLOCK=STATUS
>CENTURY=ON
>TITLE="Gemini Quotes Development in VFP 9.0"
>RESOURCE="C:\DEV\GEMINI\FOXUSER.DBF"
>RESOURCE=ON
>DEFAULT=C:\DEV\Gemini
>TMPFILES=c:\TEMP
>EDITWORK=c:\TEMP
>SORTWORK=c:\TEMP
>PROGWORK=c:\TEMP
>_GENMENU="C:\GENMENUX\GENMENUX.PRG"
>CPDIALOG=OFF
>

If you're specifying a CONFIG.FPW in the .EXE startup command line (i.e. in your shortcut) you need to prefix it with -C e.g.

Drive:\SomePath\MyEXE.EXE -COtherDrive:\OtherPath\CONFIG.FPW

Otherwise, your VFP .EXE will think it's being passed a parameter; since the first line of your .EXE is not PARAMETERS/LPARAMETERS, you get the error you're seeing.