vfp and installshield merge modules

[sdocker]

I recently had to upgrade to Installshield 2012 Spring Express so I could create a set that would install on Window 8.

I now get an error that it cannot find 2 merge modules; OLEAUT32... and MSVCRT...

Are these necessary ?

If so, where can I obtain the lastest versions?

Thanks,
Sam

 

[Olaf Doschke]

If they are needed, they are needed. You should get them from the older version or VFP itself.

In regard o MSVCRT the newest version is not what you need, but the exact version needed for the VFP runtimes.

Merge Modules are installed in C:\Program Files\Common Files\Merge Modules and that complete directory should be listed by Installhield.

The merge modules you need for VFP come with VFP, but if you simply copied over your installation folder from Win7 or an even older box and formatted already, they are lost, you would havee needed to also copy merge modules from that folder to keep them.

In regard to OLEAUT32, that most probably is related to an OLE control you used on some form, so what OLE controls did you use? The same applies, if you just copied over an OCX from some other machine, you surely have missed to also copy over the corresponding merge module coming with the OLE control or VFP itself.

Bye, Olaf.

 

[sdocker]

Hi Olaf,

I am not sure they are needed. In the installshield setup, they are checked in the "Redistributable" category, because they were checked when I used a prior version of Installshield.

How can i get them form an older version of VFP. The VFP version installed on my machine is 9.0 SP2 Version 09.00.0000.7423.

My system, Windows 7, has a folder Program Files/Common Files. (No sub folder named "Merge Modules".)

It does have Program Files (x86)/Common files/Merge Modules, but the files OLEAUT32 and MSVCRT are not listed.

I have the files msvcrt.dll and oleaut32.dll from a older installation. Could they be helpful.

In regard to the OLEAUT32, I am using MSWord automation. It works fine on my development machine, so wouldn't the necessary files be there someplace.

Sam

 

[Olaf Doschke]

On a 64bit system, the Program Files for 3bit Programs and merge modules is Program Files (x86), so that path is absolutely right.

It surprises me you don't find any merge modules there. Did you install VFP on that machine? Or did you - as I guessed - copied it over from a previous install? You didn't answer that.

If you install VFP there must be merge modules at some place.

And no, the single DLLs won't be sufficient. And yes, runtimes are needed on the target computer, otherwise your application will not work.

There are ways to install VFP runtimes without the merge modules, you can get VFP9 runtime installers, but that would be a secondary install additional to the installshield setup you want to generate.

You also didn't answer what OLE conrols you're using, so it would be a wild guess what you need for them to work.

Surely you need support DLLs like the VFP runtimes are not optional for your final setup to work.

The updated merge modules for Visual FoxPro SP2, Version 09.00.0000.7423 come with the Hotfix you or your employee must have installed, there is a readme with that hotfix telling to put the Merge Modules of VFP where they belong.

So if all else fails, reinstall VFP from CD, update to SP2, then apply the last Hotfix and always obey all instructions and you have the needed Merge Modules.

Bye, Olaf.

 

[sdocker]

Hi Olaf,

I did find merge modules in the Program files (x86) ... folder. 17 of them. But not the 2 that I'm looking for.

I did a complete install from the original CD, then i did the SP2 and then the VFP90SP2-KB968409-ENU,EXE. I followed the instructions carefully.

I have some other saved downloads that I bypassed:
VFP9SP1
VFP9.0SP2-KB955370-X86-ENU.EXE

Should I go back and redo the whole thing is sequesnce, or can I do the ones I skipped now?

I'm not sure how to tell what OLE control is being used. I use MSINET (ActiveX),

In the meantime I'll take your advice and reinstall vfp 9. and get back to you.

Thanks,
Sam

 

[Olaf Doschke]

>VFP9SP1
>VFP9.0SP2-KB955370-X86-ENU.EXE

wrong, you need VFP CD (SP0), VFPSP2 and VFP9.0SP2-KB955370-X86-ENU.EXE
The final hotfix is NO Service Pack, just a hotfix needing a SP2 Version to upgrade, so you need the SP2 beforehand. And you don't need to install SP1 before SP2.

Also see

http://rickschummer.com/blog/labels/Hotfix.html

Quote: "in the included Merge Module", so the merge modules for VFP9 are included. Of course no OLEAUT or others, just the latest VFP merge module, that is Vfp9runtime.msm. When you execute the Hotfix EXE don't just click OK read the texts, you're prompted to choose a directory for the extraction of several files and the Hotfix then extracts the files there. After that the Hotfix tells you to read the readme to follow further instruction and copy over several to their final destination, read the 968409_ReadMe.txt

The C Runtime Mergemodule is included in the install of VFP from CD. You find a list of Merge Modules, which VFP installs in HOME()+"redist.txt". If you don't find them all, repeat the VFP9 install frmo CD.

About OLE: MSINET, this is what I wanted to know, not a DLL or OCX name, that's mostly useless. Merge Modules are a sub install of several files in almost all cases, so theri name rather is the control name, not one of the file names included in the merge module. For MSINET the MSINET.MSM would be the Merge Module and it comes with VFP9 from the CD.

If you don' find everything you haven't installed properly. Take your time, read instructions, don't just click the first button you see.

Bye, Olaf.

 

[sdocker]

Thanks so much Olaf,

I did it and all VFP msm's seem to be there.

I still have a small problem with installshield. The MSM's included with Installshield 2012 are different than prior versions. Since IS 2012 does not support Windows NT or Windows 95, the pertininet msm's are no longer included, and also no longer needed.

I spoke to Installshield and am awating cinfirmation.

Sam

 

[Olaf Doschke]

OK, that's new to me, but I never did upgrade Installshield.

What are merge modules called now? Or do they instead use MSI files? If they don't support MSM any more, and don't include a module for VFP runtimes, then you're out of luck, the other thing you can redistribute in regard of VFP runteims then just are the DLL files themselves.

An alternative option also viable for windows 8 is Inno setup. Though that also does not support MSM, you can find infor in what you need for VFP in the fox wiki, the needed runtime files for VFP9 itself are described at

http://fox.wikis.com/wc.dll?Wiki~VFP9RuntimeFiles,

you just have to find out what's in MSINET.MSM or what else to redistribute for that specific control. Maybe it's indeed just the msinet.ocx

Bye, Olaf.

 

[sdocker]

Olaf,

I upgraded from IS 2010 to IS Spring 2012 because IS 2010 would not install to a Windows 8 OS. In IS you have to check the OS's you want to allow your app to install on. IS 2010 predated Windows 8, so there was not a way to include Windows 8 in the allowed OS's.

They still have the merge modules and Runtimes. They are just applicable to the current version of IS. I found the ones I was missing in a 2010 folder of IS modules. They were no longer included in the 2012 folder.

This is the way I understood the support person at IS. I believe if I was more experiended and knowledgeable, I could have figured it out myself.

Thanks again for your help and patience. It is people like you that make me a better programmer.

Sam

 

[Olaf Doschke]

In my experience you don't need to specify destination OSes, then any OS will be installed to, but surely the newest version of IS is a good installer product in itself. It's rather the legacy state of VFP merge modules making it less usable, perhaps. So the 2010 folder of IS modules seems to include such legacy merge modules, and comes with IS 2012. Do I understand this correctly?

Bye, Olaf.

 

[sdocker]

Olaf, I'm not sure.

In IS Spring 2012 you are required to pick the OS's you want your product to target. The only options are:
Windows 8
Windows Server 2012
Windows 7
Windows Vista
Windows XP
Windows server 2003
Windows server 2008
Windows server 2008 R2
Windows 2000

If a user tries to install to an OS not in the above list, it fails.

I believe there are merge modules that IS 2012 Spring doesn't have any use for, so they are not included with IS 2012 Spring.

All in all, IS works good for me. At least the features I need it for. And, I am used to it, so I avoid a learning curve.

Sam

 

[sdocker]

Olaf,

I will be off the air for several hours. If there is any more communications, I will tend to it when I return.

sam