>>>I developed a custom OLE server in VFP 6.0. I copy the files MyOLEServer.dll, MyOLEServer.VBR a target machine, run the regsvr32 command and all it´s ok, but when i try to execute one command of my class, show me the error 0x8002801d. I try this with VFP 5.0a and all it´s ok. Some idea?. Thank you.
>>
>>
>>Do you have the latest DCOM installed on both machines?
>
>This is probably complaining on my part, but shouldn't the VFP Setup Wizard distribute at least DCOM95 when you create an install program. I should have paid more attention to earlier posts about this. I did download the latest the two VFP 6 updates, FFC and Setup Wizard EXE's.
>
>The VFP 6 install complains about lack of DCOM95 when installing the ODBC drivers and when you exit the VFP 6 EXE following the install you get a 'C000' something or another exception error.
>

The problem here is the Setup Wizard's ability to manage a component install that may demand a reboot of your system (DCOM does this.) There is no built-in mechanism to resume an install if the user allows the system to reboot as requested by the DCOM install.

I've written wrapper scripts to manage the conditional installation of DCOM (the DCOM version to install depends on the OS in use, and is not always necessary.) I've used InstallShield Pro v5.1 in the past; the wrapper could also be written using the Windows Scripting Host. In any case, the strategy is to make the determination as to whether the DCOM install is needed; if it is, copy the files necessary to continue the install after DCOM completes to the local drive, including additional scripts as needed, write a registry key that will cause the continuation script to run after a reboot, and then fire DCOM. If control is returned to the script, remove the registry key and fire the continuation code at that point, otherwise, it runs after the reboot.

I have not been able to incorporate this logic into the Setup Wizard generated SETUP.STF, even by hacking the STF file. The wrapper, or a post-install executable that will run DCOM and do the above (not written in VFP, since the VFP app would require the DCOM install to have completed) has to handle this process itself. If using a wrapper, the wrapper (and the continuation script) must take responsibility for firing the Post-Setup Executable(s) needed, so do not include the Post-Setup executable in the Setup Wizard generated install.

hth,

Ed

>Could you refresh my memory as to the solutions to these problems?