More investigation and testing is needed to be sure about this, but...

Damn, it's not a silver bullet.

One of the problems is that on a fresh-formatted Win98 computer, the file OLEAUT32.DLL is present, but it's not a recent-enough version to make MSVBVM60.DLL happy. So even though I "fusion'ed" the correct OLEAUT32.DLL file to my executable, the older one installed on the system takes precedence and I still get the out-of-date file error message.

So this "fusion" app, although promising, is kind of useless for my purposes. I was hoping it would save my app from DLL hell, but it doesn't. And my app is a pretty darn simple app, it doesn't have any complicated dependencies, just whatever dependencies VB has natively.

I could still distribute it as it stands now, and link to the microsoft VB6 Runtime installer. But so far there isn't a compelling advantage to move to VB6 except for the new file dialogs. And since the current 16-bit file dialogs work OK (they're just mildly irritating now), I don't see a reason to add the extra megabytes of bloat.

I find it odd that Fusion doesn't solve my problems because that's the very root of what they're trying to do: Make it so you don't have to distribute the VB6 runtimes.

___________
Tony Fabris