Map Finder - specified module could not be found

[Denniz]

I think I've isolated why the Map Finder VB app only work for people with office or possibly VS 2005. I am using FM20.dll which is a window office component which is not redistributable. (The regular vb6 versions of some of the controls are inferior to the ones from FM20.dll.)

So although the wizard installs it does not run without an MS app that includes it installed. The article recommends installing a free MS app if you don't have Office or some substitute. Anyone having issues that can't get office should try downloading this:
Microsoft ActiveX Control Pad.

I will work to move the app to VB 2005 Express and/or get rid of the dependency as soon as possible. I am sorry for the hassle.

[grumbler]

I already have fm20.dll (in windows\system32). I also tried putting a copy of fm20.dll in the map finder application folder. Is still get the "specified module not found" error.

Better hurry that conversion to VB Express!

[grumbler]

Ok, I think I found source of my troubles:

I checked the DLL dependencies for MF_Rule_Builder.exe and found a call to IEFrame.DLL which in turn uses dwmapi.DLL.
The later is part of Vista so it's no wonder that it's missing on my XP system.

But why does IEFrame.dll call a Vista dll?
Well, I recently installed the IE7 beta and apparently some dlls where replaced in the process which now mess up the map finder app. Sigh.

[Denniz]

Originally Posted by grumbler

Ok, I think I found source of my troubles:

I checked the DLL dependencies for MF_Rule_Builder.exe and found a call to IEFrame.DLL which in turn uses dwmapi.DLL.
The later is part of Vista so it's no wonder that it's missing on my XP system.

But why does IEFrame.dll call a Vista dll?
Well, I recently installed the IE7 beta and apparently some dlls where replaced in the process which now mess up the map finder app. Sigh.

Those are shared DLLs that come with various MS apps. I think that your's is a more recent version that was left behind by IE7 beta.