VB OCX registration frustration
| Author |
Message |
|
Randy Barro
#1 / 9
|
 VB OCX registration frustration Quote:
> Is there any sure fire way of ensuring a vb app will run on 95% of
> installations? I'm so sick of creating an app only to have it fail on every
> different computer because of a missing OCX, DLL or the wrong registration
> information.
> How can I be certain that my apps will not require any other support files?
> Is it only when using "controls", eg. common dialog, richtext, etc. What is
> the point of using these tools if the app isn't portable to any other
> machine without manually including each file that it cracks it over.
> Note: I'm not using an installation program...would this help? Seems a bit
> overkill for the small apps I build...
Hi hippy-
If you don't use an installation program, you shall *not* have any
fun.;-( That's what WiseInstall, InstallShield, and the P & D Wizard are
for. Your little .exe file may be less than 100K, but it usually
requires megabytes of support files. And the installation program takes
care of your registry problems and (if your app is 32-bit under Win9x
and up) creates the uninstall info as well. The smallest app I've ever
deployed in VB was about 2.24 megs split onto two diskettes.
Welcome to Windoze, and all the joy pertaining thereunto.
Good Luck,
Randy Barrow
--
==============================================
Please remove NOSPAM from address for replies
==============================================
|
| Wed, 18 Jun 1902 08:00:00 GMT |
|
 |
|
hipp
#2 / 9
|
VB OCX registration frustration Is there any sure fire way of ensuring a vb app will run on 95% of
installations? I'm so sick of creating an app only to have it fail on every
different computer because of a missing OCX, DLL or the wrong registration
information.
How can I be certain that my apps will not require any other support files?
Is it only when using "controls", eg. common dialog, richtext, etc. What is
the point of using these tools if the app isn't portable to any other
machine without manually including each file that it cracks it over.
Note: I'm not using an installation program...would this help? Seems a bit
overkill for the small apps I build...
help
sick of ocx reg errors
|
| Wed, 18 Jun 1902 08:00:00 GMT |
|
|
|
widja..
#3 / 9
|
VB OCX registration frustration I would like to know also if anyone knows it would
be great
many thanks
widjajaf
Quote: > Is there any sure fire way of ensuring a vb app will run on 95% of > installations? I'm so sick of creating an app only to have it fail on every > different computer because of a missing OCX, DLL or the wrong registration > information. > How can I be certain that my apps will not require any other support
files?
> Is it only when using "controls", eg. common dialog, richtext, etc.
What is
> the point of using these tools if the app isn't portable to any other
> machine without manually including each file that it cracks it over.
> Note: I'm not using an installation program...would this help? Seems
a bit
> overkill for the small apps I build...
> help
> sick of ocx reg errors
Before you buy.
|
| Wed, 18 Jun 1902 08:00:00 GMT |
|
|
|
SpaceBudd
#4 / 9
|
VB OCX registration frustration Take a look at VB-powerwrap http://www.go-download.com
Quote: > Is there any sure fire way of ensuring a vb app will run on 95% of > installations? I'm so sick of creating an app only to have it fail on every > different computer because of a missing OCX, DLL or the wrong registration > information. > How can I be certain that my apps will not require any other support
files?
> Is it only when using "controls", eg. common dialog, richtext, etc. What
is
> the point of using these tools if the app isn't portable to any other
> machine without manually including each file that it cracks it over.
> Note: I'm not using an installation program...would this help? Seems a bit
> overkill for the small apps I build...
> help
> sick of ocx reg errors
|
| Wed, 18 Jun 1902 08:00:00 GMT |
|
|
|
David Ma
#5 / 9
|
VB OCX registration frustration You're right it is a bit of overkill, but unfortunately - that's
Microsoft for you. If you use the package and deployment wizard
(or application setup wizard if you're on VB5) your app will then
work a lot better. (can't guarantee 100% as I've still had some
occassional problems). The bottom line is that if you use a control
then you need to install the OCX and any related DLLs - the chances
of you manually figuring it out is a bit slim unless you have some
interrogation tools. There are other 3rd party installation packages
out there that work better than those microsoft supply (Install shield
is very popular but a bit pricy). Even if you have nothing apart from
the very basic standard VB controls then you still have to install the
VB runtimes so it's pays your money and takes your choice really.
David
Quote:
> Is there any sure fire way of ensuring a vb app will run on 95% of
> installations? I'm so sick of creating an app only to have it fail on every
> different computer because of a missing OCX, DLL or the wrong registration
> information.
> How can I be certain that my apps will not require any other support files?
> Is it only when using "controls", eg. common dialog, richtext, etc. What is
> the point of using these tools if the app isn't portable to any other
> machine without manually including each file that it cracks it over.
> Note: I'm not using an installation program...would this help? Seems a bit
> overkill for the small apps I build...
> help
> sick of ocx reg errors
|
| Wed, 18 Jun 1902 08:00:00 GMT |
|
|
|
John
#6 / 9
|
VB OCX registration frustration You gotta just an install program. We use Wise 8.1
About 6 months ago we fretted over this and other installation issues.
Our solution, which has worked great, mush less support calls:
a) Have the installation program check the current version of MS IE.
If it isn't at least 5.01, then force the user to install it. I know
what you're thinking, but we've discovered that having a recent
version of MS IE installed solves 99% of workstation problems !
b) Do the same thing for MDAC (ODBC 32)
----------------------------------------------------------------------
Quote:
>Is there any sure fire way of ensuring a vb app will run on 95% of >installations? I'm so sick of creating an app only to have it fail on every >different computer because of a missing OCX, DLL or the wrong registration >information. >How can I be certain that my apps will not require any other support files?
>Is it only when using "controls", eg. common dialog, richtext, etc. What is
>the point of using these tools if the app isn't portable to any other
>machine without manually including each file that it cracks it over.
>Note: I'm not using an installation program...would this help? Seems a bit
>overkill for the small apps I build...
>help
>sick of ocx reg errors
(please remove "NoSpam_" from return address to respond directly)
|
| Wed, 18 Jun 1902 08:00:00 GMT |
|
|
|
ian Lain
#7 / 9
|
VB OCX registration frustration Hi "hippy",
As per other posters recomendations you just gotta take the hit of deploying
your 10Kb app in a packge of 3Mb+!!!
But on the plus side what you can do, depending on your "audience", is build
a dummy app with all your possible controls (and use them in the dummy app
otherwise the packager may remove the reference) and get the user to install
that initial 3Mb package and then you should be able to send them any of
your exe files directly and they should be able to run without being
packaged (they have by default installed all the controls you'll be using).
At least it *seems* to work for me as I copy my exe's to my works machine
(I'm '98 and it's NT) and the only time they don't seem to run is when I
introduce new controls not used by my previous installed apps.
I haven't created a dummy app but previous installs have sufficed to build
the correct environment on my works machine to enable me to copy raw exe's
without problem.
OK it's a sledge hammer to crack a nut by installing the dummy app with all
the anticipated controls which is just junked but then the install wizzard
is a sledge hammer anyways.
but it does simplify later program installs/downloads.
I use the standard P&D wizzard but I assume the principle is the same
whatever install/packager you choose?
Cheerio,
ian Laing
Quote: > Is there any sure fire way of ensuring a vb app will run on 95% of > installations? I'm so sick of creating an app only to have it fail on every > different computer because of a missing OCX, DLL or the wrong registration > information. > How can I be certain that my apps will not require any other support
files?
> Is it only when using "controls", eg. common dialog, richtext, etc. What
is
> the point of using these tools if the app isn't portable to any other
> machine without manually including each file that it cracks it over.
> Note: I'm not using an installation program...would this help? Seems a bit
> overkill for the small apps I build...
> help
> sick of ocx reg errors
|
| Wed, 18 Jun 1902 08:00:00 GMT |
|
|
|
C.Merso
#8 / 9
|
VB OCX registration frustration You can get a list of the dependant files for your version of VB and the
activeX controls and so forth that you add to your project and then check if
they exist in the various directories (usually winsys. directory). If they
don't exist you could install them one at a time. But basically you would
have to do the job of an installer.
If you want to save time and unecessary effort you will definitely need to
use some sort of installation program. I'm no expert in vb, but I have had
exactly the same problems in the past and I was using an installation
program.
Vb uses some files that are common to the version and no others eg. the
runtime files. Windows does not ship with all these necessary files for all
the versions of vb and so they must be included(for your version at least)
in your setup package.
You can download a free installer or use the package and deployment wizard.
You will find that the p&d wizard is a little limited, but it registers the
OCX files and others for you automatically. A lot of other installers don't
do this as far as I know. (not the free ones that I tried anyway)
While you're making small programs that don't have many extra files it does
seem pointless to use an installer and create your app seem larger than it
needs to, but the more files you add the more you appreciate tools like
this.
Best regards
Chris Merson
Quote:
>I would like to know also if anyone knows it would >be great >many thanks
>widjajaf
>> Is there any sure fire way of ensuring a vb app will run on 95% of
>> installations? I'm so sick of creating an app only to have it fail on
>every
>> different computer because of a missing OCX, DLL or the wrong
>registration
>> information.
>> How can I be certain that my apps will not require any other support
>files?
>> Is it only when using "controls", eg. common dialog, richtext, etc.
>What is
>> the point of using these tools if the app isn't portable to any other
>> machine without manually including each file that it cracks it over.
>> Note: I'm not using an installation program...would this help? Seems
>a bit
>> overkill for the small apps I build...
>> help
>> sick of ocx reg errors
>Sent via Deja.com http://www.deja.com/
>Before you buy.
|
| Tue, 11 Mar 2003 13:09:19 GMT |
|
|
|
El Sydr
#9 / 9
|
VB OCX registration frustration Try BitArts Fusion and see if that helps.
Quote: > Is there any sure fire way of ensuring a vb app will run on 95% of > installations? I'm so sick of creating an app only to have it fail on every > different computer because of a missing OCX, DLL or the wrong registration > information. > How can I be certain that my apps will not require any other support
files?
> Is it only when using "controls", eg. common dialog, richtext, etc. What
is
> the point of using these tools if the app isn't portable to any other
> machine without manually including each file that it cracks it over.
> Note: I'm not using an installation program...would this help? Seems a bit
> overkill for the small apps I build...
> help
> sick of ocx reg errors
|
| Wed, 18 Jun 1902 08:00:00 GMT |
|
| |
|
