Since Microsoft wants to sell VFP to its customers that is one limitation it would never put into its product!!! :)

One difference I can think of though is that some of the development tools available in the application are not available in the EXE. For example, it won't let you bring up the debugger in the EXE. It also won't let you bring up the Query designer or Form designer. So, if you ever wanted to give your users the ability to create their own ad-hoc reporting you would have to use something other than the Query designer.

Also one thing I became acutely aware of is that you will want to use the SETUP wizard that comes with VFP when you go to install the EXE. There are many other modules you need with the EXE for it to run and the easiest way to make sure all those modules are installed is to have the SETUP wizard automatically include them with the installation process.
Being the genius that I am (NOT!!), I tried installing my application without using the SETUP wizard. After many days of attempting this I finally bowed to MS and used the SETUP wizard <grin>.

GeneS



>I was told by some fellow developers that I must make all of my forms in my application modal since I plan on creating an EXE from the final application to distribute to users without FoxPro.
>
>I can't find confirmation of this in any of my documentation and was wondering if any of you knew this to be the case or not.
>
>Also, are there any other special considerations I should keep in mind when developing my app which will eventually become an EXE?
>
>Many thanks as always,
>
>Mandy