I don't know if they install them identically. This is farily big organization and I can't say that they know themself.

As far as registry, I am reluctant to hack into the registry on their computer. I may (or may not) make my application work but the liability is such that I may be responsible for any other problem they have with this PC (with some other application).

Thank you.

>Are the office computers installed identically? If they are, then do a search on every DLL and EXE on the machine and compare the set from a machine that works, and a machine that doesn't work. That may identify an odd problem such as an errant DLL or EXE.
>
>Next, iterate through the registry and for any character strings you find a DLL or EXE filename that exists, see if it has a parent class and note that, or note its immediate parent, and save all of those entries to a table on the working machine, and on the non-working machine. Do a comparison to see what's different.
>
>A little trial-and-error and you should be able to identify what's different. If the machines are identical, and their setup is identical (such as in an Enterprise rollout by a computer user type, such as a "standard office" computer), then it should be easy to track down the variance. Identify the differences, and then fix them either one by one if the list isn't too big, or block by block if there are many more.
>
>
>
>>The customer has already reinstalled Windows 7, so I can't ask them for more. And I can't ask them to replace the computer until I exhaust all attempts in solving the problem. I have scheduled a time next week when I can connect to this computer remotely and try various things. Of course if nothing resolves the issue they will have to replace the PC. As far as "why spend countless hours", my answer is for a good will of the customer. I don't advertise my product and 99.99% of my sales comes from customers recommending to other companies. Or the key person from the company leaves and goes to work for another company and remembers my product. So I see investing time in resolving the issue as a marketing effort too.
>>Thank you
>>
>>>Although I have not experienced this issue before, I found that you just can't solve some problems no matter how much you try if in fact it is something odd about this one in a million problem computer. Why spend countless hours chasing after something that might not never happen again. I just tell the client there is something odd about this setup of this computer, and the program will not run on it - and they will need another computer instead (as they are already using many), or perhaps do a complete rebuild of the Windows OS and that would probably fix it.
>>>
>>>I have had to do this only a handful of times in 30 years, but never had a client that was not understanding (especially if they knew it was working fine on all their other computers).
>>>
>>>>>>Hi,
>>>>>>
>>>>>>Again, a customer is having a problem running VFP 9 application. When they start the application .EXE file they get the window DO and the File of type shows "Program (*fxp)". I have tried several different .EXE programs (different programs but all built with VFP 9). The customer also tried to reinstall Windows 7 completely. The strange thing is when they reboot the computer the program(s) work one time (no problem). When they close a program and start again, the problem with DO *.FXP appears again until they reboot the computer.
>>>>>>
>>>>>>Any suggestions to where to look? TIA
>>>>>
>>>>>
>>>>>Did you check the "errors" when you build the project? Check if there are any files missing in the project. Also check that the programs are included in the project. If you are using macro or any indirect way of running a prg, be sure that said prg is included in the project, if the project includes other applications, check for the same issues in the other projects too.
>>>>
>>>>You see, the problem (of DO *.FRX) happens if we run any VFP 9 executable. I tried several. I think if I make a "Hello World" executable, we would have the same problem. Also, the same application(s) runs on many other computers of this customer computers and many computers of other customers. So, as much as I am sure, there are bugs in the application, this particular problem is brought about by something on this particular PC (hardware or some setting in Windows 7).
>>>>Thank you.