Home All Groups Group Topic Archive Search About
Author
12 Oct 2005 1:50 PM
Robert Dormer
Hello all,

I'm trying to move a VB 6.0 app from the machine it was developed on to
other machines.  The app uses ActiveX controls like DBGrids and progress
bars.  When I try to run it on other machines, I often get the dreaded error
429.  Even more perplexing, I copy the controls onto the machines and
register them, and still get the error.  So apparently the VB IDE install is
doing something that I'm not aware of that gets these controls on to the
system.  Can anyone shed some light on what's going on?

Author
12 Oct 2005 3:05 PM
Ralph
Show quote Hide quote
"Robert Dormer" <r.dor***@www.digdevinc.com> wrote in message
news:enDqXxzzFHA.736@tk2msftngp13.phx.gbl...
> Hello all,
>
> I'm trying to move a VB 6.0 app from the machine it was developed on to
> other machines.  The app uses ActiveX controls like DBGrids and progress
> bars.  When I try to run it on other machines, I often get the dreaded
error
> 429.  Even more perplexing, I copy the controls onto the machines and
> register them, and still get the error.  So apparently the VB IDE install
is
> doing something that I'm not aware of that gets these controls on to the
> system.  Can anyone shed some light on what's going on?
>

You are missing a component.

Whenever you install a program on another Windows box you need to create a
'package'. There are numerous alternatives, but for now open the P&D
application (Package & Deployment) and follow the step by step dialogs.

-ralph
Author
12 Oct 2005 3:11 PM
Jeff Johnson [MVP: VB]
"Robert Dormer" <r.dor***@www.digdevinc.com> wrote in message
news:enDqXxzzFHA.736@tk2msftngp13.phx.gbl...

> I'm trying to move a VB 6.0 app from the machine it was developed on to
> other machines.  The app uses ActiveX controls like DBGrids and progress
> bars.  When I try to run it on other machines, I often get the dreaded
> error 429.  Even more perplexing, I copy the controls onto the machines
> and register them, and still get the error.  So apparently the VB IDE
> install is doing something that I'm not aware of that gets these controls
> on to the system.  Can anyone shed some light on what's going on?

Do you have the source? If so, create a setup package and INSTALL, do not
simply copy, even if you think you can find every control.