>>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?
>
>A blast from the past... something somewhere installs a newer version of an ActiveX or other COM thingy, possibly in a different location, and removes the one your app used. Your app's runtime detects a missing component and requires that it be reinstated. The solution was to have your version of those in your app's folder.
>
>I guess it wouldn't be any of those that your forms use, as these wouldn't be detected until the form is opened, so I guess it would be one of those elementary ones, like comctls.
>
>Now which components, and specially what are their filenames, ouch... takes some time to investigate, as m$ has obfuscated the issue, the names are mostly unrelated to each other, and you need to know where to look for the relation. Since I'm generally not using anything m$ for a few years now, ... you'll manage.

As I just described to Hank, the application EXE and the set EXE are two different programs. So, if any ActiveX components got wiped out or whatever, the main application EXE would show an error. The main EXE knows nothing about the SETUP.EXE
My "blast from the past" points to some program - for some reason I remember AUTO CAD - that would make the SETUP.EXE start without anyone starting it. But both customers said they do not have CAD on their PC.
I suspect that M$ added something to the OS and now two executables start at the same time.
Thank you.