>>>>>>>I am in my first attempt at building a stand-alone .EXE. I have built .app's before, and I now have one that I want to build into an .EXE. Do I need to put any files into my project, if so where. All advise is greatly appreciated. Thanks.
>>>>>>
>>>>>>
>>>>>>What version of FoxPro?? Only FoxPro DOS can build stand alone EXEs. All other versions require support libraries.
>>>>>>
>>>>>>Craig
>>>>>
>>>>>I am using VFP 3.0b. What support libraries do I need, and where
>>>>>do they go? thanks for the help.
>>>>
>>>>Distributing VFP app, you have to use Setup Wizard which will collect many files (including support library) automatically into installation package. Basically, there are no ways to distribute VFP app avoiding Setup process, but if VFP already installed on some machine, you could just move 'alone' exe file over there and run.
>>>
>>>
>>>So if I use the wizard it will automatically grab all the extra files
>>>that I need. I will give it a go. thanks.
>>
>>Yes, extra system files. But all your own files like Config.fpw, tables, some third-party OCXs, etc. should be included to distribution tree before you start Setup Wizard. Don't worry about form,reports,etc (they should not be included).
>
>So Forms and reports do not go in the distribution tree?
>I used the setup wizard, got through it, but on trying to install the application I got an error saying bad source file in INF file. Any Ideas what the problem there is? thanks

I had some problems at first also. vfp5.0 works perfert but 3.0b gave me trouble. i suggest put vfp300.esl (which is in your windows/system directory and is about 3.7meg)into the same directory in the machine you want your exe to run. use the build to make an exe file from the program manager. you need to include all your forms and code in the exe. generally do not include the tables. transfer the exe to the new machine and it should work.
the above will not work with vfp5.0

jim jacques