>>>>>> But why won't a compiled form (.exe) run after you have
>>>>>>built an app file using that form. And exactly what is the difference between
>>>>>>an app and an exe. Finally how do you prepare to install an application
>>>>>>whether app or exe with all necessary libraries so it will run on a different
>>>>>>workstation that has never had a foxpro applicaiton installed before?
>>>>>
>>>>>Derek,
>>>>>
>>>>>In a nutshell, you need an installed vfp to run an .app, whereas .exe run on PC's where no VFP has been installed. Mind you, like most things under Windows .exe need to be installed on PC's where VFP was not installed to copy a few .DLls in the windows\system and do other things.
>>>>>
>>>>>In development I simply compile toward an .app that resides in the main development directory, and when I am ready to deploy I generate an .exe in a subdirectory and copy from there.
>>>>>
>>>>>HTH,
>>>>>
>>>>>Marc
>>>>
>>>>
>>>>I think I understand what the difference between an app and an exe is now
>>>>but why after I have removed all apps related to this exe and recompiled it
>>>>and renamed all other app to apx doesn't it run the recompiled exe files?
>>>>Thank you Derek.
>>>
>>>Derek, if you run the Exe (i.e. go to Windows Explorer, click on Exe file), then it runs. What exactly you mean saying that you cannot run Exe?
>>
>>What Happens Edward is that on the development machine only or any
>>machine where the setup wizzard's installation disks were used to install
>>the application the exe is double clicked and begins to load including
>>a warning ( which is normal for these machines) that a dll that is being loaded
>>is for NT ( which its not we just have the latest version of 95 which uses a dll
>>that is newer than foxpro but this happens on all foxpro loads then the screen
>>start to load with the foxpro normal template then dies out disappearing completely without warning. I did indead compile it (the form within a different
>>project) once as an app out of curiosity and apparantly am to be punished
>>forever. Other forms (scx) can be compiled and run normally. But even changing the name of this form and putting it into a differerent project does not help. Somehow its the app property must have become embedded into the
>>form itself. How do I get it out?
>
>Sorry, it's silly question, but do you include READ EVENTS?
It most certainly wasn't a silly question since I hadn't. But why didn't
I need this command on machines I hadn't compiled this form as an app or
on this machine before then. Also since I added this command to the
activate sheet of the form this program now doesn't want to shut down. The X is greyed out on the form as is close on the file menu and if I use the X on the
vfp itself it says " Cannot Quit Visual FoxPro. This has happened since I added
the read events command.

One more thing since I'm bothering you anyhow. I print three reports from command buttons on this form. Each use " report form *.frx to print where *
is letter.frx or letter2.frx or total.frx. Only one displays on the screenand won't
go away without closing foxpro. This on a machine with the version of the
program that works properly without the read events command as the app
version of the program was never on that machine. Many thanks-Derek.