>>Dear Richard,
>>
>>I also use my own setup-by-hand method.
>>
>>The MS KB article Q190869 list the necessary files to be installed to run VFP6:
>> filename /version
>> -------------------------
>> asycfilt.dll /2.30.4261
>> msvcrt.dll /6.00.8168
>> oleaut32.dll /2.30.4261
>> olepro32.dll /5.0.4261
>> stdole2.tlb /2.30.4261
>> vfp6r.dll /6.0.8167
>> vfp6renu.dll /6.0.8167
>>
>>To run active documents, the following file is required:
>> vfp6run.exe/6.0.8167
>>
>>All of these file copy into system dir. And you must register the following files:
>>
>> vfp6r.dll
>> oleaut32.dll
>> olepro32.dll
>> vfp6run.exe (I cannot register it, I think the original article is buggy)
>
>No, it indicates that other components needed by the target system are lacking. Your "roll your own" approach isn't working. This also does not address the issues of MTDLLs, or the creation of registry keys beyond those generated by self-registration code. Also, you don't register an .EXE using REGSVR32.
>
>I doubt seriously that you've made the necessary accomodations for deferred copy and registration, where any of the affected files at an earlier version are present and running.
>
>Doing an install wrong is infinitely more frustrating and costly than buying a tool that does installs properly. Keeping up to speed with required files in the light of Service Packs is much more demanding than you might realize.
>
>DON'T TRY TO DO INSTALLS LIKE YOU DID IN DOS.

Dear Ed,

You are probably right. (it is an official MS article. )
VFP6Run.Exe is not necessary for me, because I donnot use active documents.

Anyway, I use my own install program without any problem. (It is localized. Built in VFP intall is not localizable.) Of course, I have to register all OLE components and have to check dll version numbers and so on.
An istall program is just a program too, not a "mystery".


bb