|
-
Nov 25th, 2007, 08:58 AM
#1
Thread Starter
Frenzied Member
Missing OCX
This is my fist attempt at a proper installation of anything I have written, so my apologies if this is very basic or simple
I am using Inno Setup for this.
I was of the belief that when the app is compiled into an exe file, it also included all of the ocx and dll files, eg vbSysTrayTools.dll - not windows dll files.
Is this not the case?
I have installed Microsoft Virtual PC 2007, and loaded Win XP onto it and then tried to install my app onto it.
It seemed to install ok, no error messages, but when I went to run it, it had the error message:
MSMAPI32.ocx or dependancy not registered, or file is missing
Do I have to somehow manually add these?
-
Nov 25th, 2007, 10:21 AM
#2
Re: Missing OCX
OCX's and DLL's are not put into the executable - you need to add them to your setup package (the exception to this is when you add the code version of an OCX to your project, in which case it is compiled into your program).
I don't use Inno Setup myself, but in the FAQs at the top of this forum are a couple of links to articles on their site, which explain how to properly create a setup package for VB6 programs with Inno Setup. There is also a Microsoft article which may give you useful background information.
-
Nov 25th, 2007, 10:50 AM
#3
Thread Starter
Frenzied Member
Re: Missing OCX
Thanks si
I take it you only mean the dll files such as vbSysTrayTools.dll not the system dll files?
What set up package do you use?
Does PDW do this for you?
Basically I am looking for the easiest way to package this app, for the few people that are going to be using it.
-
Nov 25th, 2007, 11:00 AM
#4
Re: Missing OCX
You need all of the DLL's and OCX's that your program uses - which includes the ones in your References and Components lists, as well as the VB runtimes.
I personally use the Visual Studio Installer (VSI), which you can download from MS (I think there is a link to it in the FAQs). It has a VB6 template, so will automatically add the required files for you (but I think MDAC etc need to be added separately). It is fairly easy to customise the setup process, and that looks much better than the standard P&DW version too.
While P&DW can be good, you typically need to modify it (the VB6 source code is provided!) to suit your needs, and to work around various bugs.
-
Nov 25th, 2007, 12:29 PM
#5
Re: Missing OCX
I believe inno setup has a wizard for you to include dependancy files.
The P&D Wiz doesnt, you have to do it manually.
VB/Office Guru™ (AKA: Gangsta Yoda™ ®)
I dont answer coding questions via PM. Please post a thread in the appropriate forum. 
Microsoft MVP 2006-2011
Office Development FAQ (C#, VB.NET, VB 6, VBA)
Senior Jedi Software Engineer MCP (VB 6 & .NET), BSEE, CET
If a post has helped you then Please Rate it! 
• Reps & Rating Posts • VS.NET on Vista • Multiple .NET Framework Versions • Office Primary Interop Assemblies • VB/Office Guru™ Word SpellChecker™.NET • VB/Office Guru™ Word SpellChecker™ VB6 • VB.NET Attributes Ex. • Outlook Global Address List • API Viewer utility • .NET API Viewer Utility •
System: Intel i7 6850K, Geforce GTX1060, Samsung M.2 1 TB & SATA 500 GB, 32 GBs DDR4 3300 Quad Channel RAM, 2 Viewsonic 24" LCDs, Windows 10, Office 2016, VS 2019, VB6 SP6 
-
Nov 25th, 2007, 10:05 PM
#6
Re: Missing OCX
The Inno Setup Wizard does NOT find dependencies, That would be Inno Script that does that.
Also please read Installation Problems It should give you some insight on the installation process...
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|