>>>>I think I have been very carefull in the process. I have checked all the runtimes (I'm using VFP 7), as well as the localization file for spanish. I have included the C++ files too, and all the merge modules for the controls used in the application.
>>>>I have double checked them, and besides I have run the static and dynamic scanners for dependencies.
>>>>
>>>>The problem arises for COM registration. When I run the installation process, the EXE runs OK, but I have no access to the COM functions. It's something like InstallShiled does not find or recognize the .TLB and/or .VBR files associated with my EXE.
>>>>
>>>>Any ideas?
>>>
>>>I can't think of anything else at this point.
>>
>>Thanks anyway. I will try to go back and build the entire thing from scratch one more time to try to make it work.
>
>I will be adding a VFP COM (DLL) to a project in a few weeks. I have been reviewing ISE (in VFP 8) to try and understand what to do. Sometimes my apps includes fonts. Until last week, I had relied on a procedural install for fonts. Then I learned that I needed to right click the fon and "name" it, and installer would do it all for me!
>
>Are you doing a test install on the same computer the project is on? The COM is already registered on that system, so I wonder if there is a conflict there.
>
>I just read "New DLL Custom Action Function Prototype" in the IS help. I don't know what it means, but if you learn, make sure to get back:-)

Sorry I did not answer earlier. The COM is already registered on my system, but it should not bother to the build process.
I have been fighting with IS Express this week, and I have not been able to correct this. Everything goes OK with the IS version that comes with VFP 7, but InstallShield Express fails to recognize COM functions. I have changed merge modules from directories, cleaned them, ..., but it still does not work. Beats me.