Can I use/reference an OCX in a different way?
in [Visual Basic]
|
From: Tony Toews [MVP] on 4 Nov 2009 22:40 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. ;-) Hehehe Now that would be an amusing XKCD cartoon. Tony -- Tony Toews, Microsoft Access MVP Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ For a free, convenient utility to keep your users FEs and other files updated see http://www.autofeupdater.com/ Granite Fleet Manager http://www.granitefleet.com/
From: Tony Toews [MVP] on 5 Nov 2009 17:34 "Karl E. Peterson" <karl(a)exmvps.org> 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? > >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. BTW when I look at http://support.microsoft.com/kb/192461 I'm thinking the only file I'd really need to include in the folder would be MSVBVM60.dll as all the other files are in the Windows OS. Well, who knows about Windows 8. Tony -- Tony Toews, Microsoft Access MVP Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ For a free, convenient utility to keep your users FEs and other files updated see http://www.autofeupdater.com/ Granite Fleet Manager http://www.granitefleet.com/
From: Karl E. Peterson on 5 Nov 2009 18:10
Tony Toews [MVP] wrote: > "Karl E. Peterson" <karl(a)exmvps.org> 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? >> >>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. > > BTW when I look at http://support.microsoft.com/kb/192461 I'm thinking > the only file I'd really need to include in the folder would be > MSVBVM60.dll as all the other files are in the Windows OS. Well, who > knows about Windows 8. Worst case, you could probably include all those files in the folder, and they'd always be used. I believe each of those are just dirt-standard DLLs, and LoadLibrary always looks in the app.path first... Dynamic-Link Library Search Order (Windows) http://msdn.microsoft.com/en-us/library/ms682586(VS.85).aspx -- ..NET: It's About Trust! http://vfred.mvps.org |