Can I use/reference an OCX in a different way?
in [Visual Basic]
|
From: Eduardo on 3 Nov 2009 10:08 Karl E. Peterson escribi�: > > Okay, yes, I am now. Again. > > I just built a brand new Windows 7 Enterprise box from scratch. Upon getting it up, > I stuck some VB5 authored EXEs in a folder, and when I tried running them I got > this: > > The program can't start because MSVBVM50.DLL is missing from your > computer. Try reinstalling the program to fix this problem. > > So I copied that DLL from another machine into the same folder as the EXEs, and they > all worked perfectly. I then renamed the DLL, and again the EXEs generated the > above failure. Renamed it back how it should be, and they work. > > What more can I try to make it fail as you say you did? Humm... it was about ten years ago, I believe it was under Win95. I'm not able to test it right now. I'll tell you what I remember: I wanted to make a CD to install a program, with a presentation screen like the one that the Visual Basic 5 installation program had. But I soon realized that it required the runtime installed. Anyway I tested it. What I don't remember now is if I tested it in a directory or in a CD. What I know is that with VB4 it worked. I finally made it in VB4. I still have it and use it when someone ask for the CD. I'm sorry that I can't provide more details, it was long time ago. What I can say is that I only referenced the Dlls that are referenced by default in a new project (may be two or three, I don't remember exactly). But I do remember that just copying the VB5 Dlls I got an error message when trying to run the program. I don't know what else to say, I should set up a machine with Win95, but I can't do it right now.
From: Paul Clement on 3 Nov 2009 10:52 On Fri, 30 Oct 2009 12:48:03 -0700, "Karl E. Peterson" <karl(a)exmvps.org> wrote: � Paul Clement wrote: � > � Now if MS does stop including the VB6 runtime in Windows 8 I wonder if � > � this could be used to include the VB6 runtime with your app? � > � > It might be a moot point if there is no 32-bit version of, or subsystem in, the � > next version of the OS. � � LOL! Reaching for that Golden Ring, are ya, Paul? � � Fearmongering at it's finest, yessiree... Yes and I'm sure you will be screaming with outrage and writing about it once it does happen, wondering how Microsoft could do this to a product they no longer support. ;-) Paul ~~~~ Microsoft MVP (Visual Basic)
From: Paul Clement on 3 Nov 2009 10:55 On Fri, 30 Oct 2009 16:44:44 -0600, "Tony Toews [MVP]" <ttoews(a)telusplanet.net> wrote: � Paul Clement <UseAdddressAtEndofMessage(a)swspectrum.com> wrote: � � >� Now if MS does stop including the VB6 runtime in Windows 8 I wonder if � >� this could be used to include the VB6 runtime with your app? � > � >It might be a moot point if there is no 32-bit version of, or subsystem in, the next version of the � >OS. � � With any luck I'll be dead by then. I don't think I would want to tie Microsoft's Product Lifecycle to my own. ;-) Paul ~~~~ Microsoft MVP (Visual Basic)
From: Paul Clement on 3 Nov 2009 11:03 On Fri, 30 Oct 2009 12:55:57 -0700, "Karl E. Peterson" <karl(a)exmvps.org> wrote: � A common misconception about the VB runtime is that it needs to be � installed/registered. Just not the case. You can run a ClassicVB application � directly off a CD if the runtime exists in the same folder as the exe, just as it � would work with any other standard DLL. It's really that simple, until you start � dragging other ActiveX stuff into it. Which most developers do since ActiveX/COM is a significant feature of the product. Paul ~~~~ Microsoft MVP (Visual Basic)
From: Karl E. Peterson on 3 Nov 2009 14:09
Eduardo wrote: > Karl E. Peterson escribi�: >> What more can I try to make it fail as you say you did? > > Humm... it was about ten years ago, I believe it was under Win95. > I'm not able to test it right now. > I'll tell you what I remember: > I wanted to make a CD to install a program, with a presentation screen > like the one that the Visual Basic 5 installation program had. > > But I soon realized that it required the runtime installed. > Anyway I tested it. What I don't remember now is if I tested it in a > directory or in a CD. I just tried it with a CD. Actually, I created an ISO, which I used as a virtual CD in a clean Windows 95b VM. It contained four files - OpSys.exe, OpSys6.exe (http://vb.mvps.org/samples/OpSys), msvbvm50.dll, and msvbvm60.dll. The VB5 build ran on first double-click. The VB6 build balked at OLEAUT being out of date... The file 'OLEAUT32.DLL' is out of date. This program needs a newer version." But I don't foresee that being an issue for too many folks, as virtually no one targets Win95 anymore. > What I know is that with VB4 it worked. I finally made it in VB4. Yeah, that makes sense. That was the version of VB that was coincidental to Win95, so it would expect the same version of OLEAUT32. Could be that by the time 950B shipped, VB5 worked as well? > But I do remember that just copying the VB5 Dlls I got an error message > when trying to run the program. > > I don't know what else to say, I should set up a machine with Win95, but > I can't do it right now. Ah well, I guess all we can say is that if someone wants to support a machine that old they'd better be sure to test it! I can tell you there's no (runtime-related) problem (that I've yet encountered!) using VB5 exes on Windows 7 as long as the runtime is either installed or on the LoadLibrary search path. -- ..NET: It's About Trust! http://vfred.mvps.org |