>>>>>>Hi,
>>>>>>
>>>>>>I have a customer who emailed me the following problem. Every time they start the VFP 9 application (my app), the setup program starts. The Setup program is that one that installs the run-time DLLs on the PC. And this SETUP already ran some long time ago.
>>>>>>What would make the run-time install being called on every start of the application?
>>>>>>
>>>>>>TIA
>>>>>
>>>>>How about they are starting the wrong exe?
>>>>>
>>>>>One of the reasons when I leave an install on a customer machine I add .zip as the suffix. :)
>>>>
>>>>This happens with a number of people in this organization. The application and the setup program are two different programs. If they were starting the wrong exe, it would stop after the the program does its job.
>>>
>>>I try as hard as I can, but all I remember is something with the Installer must gone wrong. A lot of people had this problem as the ISD express delivered with VFP comes up, and with the development computer itself. But it was a one-time fix and I don't get it out of my brain. Try to search this place.
>>>
>>>What do you use to deploy the code to your customer?
>>
>>The VFP9 DLLS are simply reside in the application folder, on the server. So, when the application starts (using a desktop shortcut pointing to the EXE in the application folder, on the server), the application uses these DLLS. The installer is built using InnoSetup and it installs a couple of ActiveX components from DBI Tech.
>>I am trying to schedule a GoToMeeting with the customer to see for myself what is going on. Maybe I will see what they don't see.
>
>The ActiveX comes with all dependencies? And it looks like a VFP Installer starting?

I don't understand the question about "dependencies". The application starts and shows a toolbar - which is a DBI Tech ActiveX control. If the DBI Tech Active X control is not installed or damaged, the application would simply show and error. The application does not know that there is another EXE that installs the DBI Tech ActiveX control. Usually if the application shows an error, customer reports it to me, and I tell them to run the SETUP.EXE which installs the DBI Tech ActiveX control. Now when the application starts, it AUTOMATICALLY starts the SETUP.EXE (the program that installs the DBI Tech ActiveX control). But nowhere in the application there is a code that points to the SETUP.EXE.
Does it explain how it works?