HELP Runtime error 429!!!

[irenavassilia]

Hi I have a visual basic program that i have created for my client on my machine which of course works wonderful.
Now that i have copied the executable program on my client machine, it gives me the Runtime error 429 ActiveX object cannot be created.

I have all the correct dlls on my clients computer. Could this be because i am using .ocx controls?

I have looked all over google for this error, and found many many resolutions but non that solve mine!

I'm lost, im not so new to VBA but when it comes to the installations im lost! HELP... please.

Thanks you,

Regards, irena

 

[HughLerwill]

<<Could this be because i am using .ocx controls?>>

So you will need to copy over the .ocx files too; have you done than?

Not quite sure if you are using VBA or VB6 I guess the later because you speak of the 'executable program'; if VB6 you should be using an installer program; the package and deployment wizzard is supplied with vb6.

 

[irenavassilia]

Yea its a VB6 program, and I have the executable already set up on my clients computer.
I went through all the controls that are being used in the program which is actually just an AccpacGL1100.ocx control. I have copied it over to my clients computer, checked all of the dll's (they're all there).
I thought maybe it could have been the windows script, reinstalled it and still the same problem.
I'm all out of ideas... I've tried everything recommended on google too, and still nothing effects this error.
Thanks for your reply, hopefully I can figure this out..

 

[HughLerwill]

Could be your ocx/dlls are not getting registered properly when you just copy them over, re my previous advise to use a proper installer.

 

[irenavassilia]

Yea you're probably right, where would i get this installer?

 

[irenavassilia]

OK, and once I have this installer, so I just install it on my clients computer?? Thanks alot.

Regards,

Irena

 

[irenavassilia]

I copied over the setup1.exe which is the package and deployment wizard file into C:\Program files\Microsoft Visual Studio\VB98\Wizards\PDWizard\

Still the same error..

Thanks.

 

[HughLerwill]

To use the package and deployment wizard;

Drop the Add-ins menu in the VB6 IDE.
Select Package and Deployment wizard if it is listed.

If it is not listed select 'Add-in Manager' and tick the 'Load on Startup' option and the 'loaded/ unloaded' options; click Ok.

You should be in business.

 

[irenavassilia]

The only one listed in the Add-ins drop down is the Component Service Add-Ins.

1)Component Service Add-Ins (includes Load on Startup and loaded/unloaded checks)
2)DTC Framework
3)Microsoft Visio UML
4)Visual Modeler Add-in
5)Visual Modeler Menus Add-in

Do i have to check off any of the five above too?

Thanks.

Regards,

Irena

 

[irenavassilia]

I've created the installation package, one of the Program works now without the error however the other program still gives me the same error, twice.

lost...

Regards,

Irena

 

[HughLerwill]

>Do i have to check off any of the five above too?

No just the Package and Deploment wizard.

>one of the Program works now without the error however the other program ...

At the start of this we had only one program! Now we have two! So what is special about this one?

 

[irenavassilia]

lol.. Actually theres nothing special about this one at all.. it only uses 3 ActiveX controls.

- common dialog control
- rich textbox control
- AccpacGL1100 control

I've re-registered all of these controls just incase they didnt registered correctly when I copied them over.
Weird stuff I tell ya, I have no clue whats going on with that program... I've been sitting here all day re-registaring all these dlls and ocx's files all day.. lol fun!

 

[HughLerwill]

So did the first program use the same three ActiveXs?

>when I copied them over..
So are you now using the P&D wiz to install the files or still manually copying them?

 

[irenavassilia]

I copied them over and registered them manually. The other program only used the AccpacGL1100.ocx control.
So it probably has to do something with one the other two controls. I'll re-check them tomorrow at work to make sure they are all in the correct folders.

Thanks.

Regards,

Irena

 

[BobRodes]

What has to happen is that all the dlls and all the ocxs that your program exe uses have to be installed (meaning present on the disk and registered) on your client's machine. The error "ActiveX object cannot be created" means that this has not been done.

So, either you HAVE done it and the computer is giving you this error for its own fractious reasons, or you HAVEN'T done it and the computer is giving you the error because you haven't done it. Forgive me, but my money's on the latter. If you've been sitting around all day registering dlls and ocxs, the first thing that comes to mind is that there's another dll or ocx it's looking for that you haven't installed yet.

Now, that said, it's also possible that your application is looking for a system dll whose version number is newer than the one on your client machine. If you run into that problem, the P&D wizard won't help you. For more information on that situation, check thread222-561173.

In any case, it's a BAD idea to hand install a VB program. Use a packaging wizard. There are a couple of others to look at: the Visual Studio Installer and INNO Setup.

Bob

 

[HughLerwill]

>I copied them over and registered them manually

You are not listening. I'm done.

 

[irenavassilia]

ok. I did use the packaging wizard, it only helped me with the first program. Like Bob was saying that maybe its looking for a system dll.

 

[BobRodes]

If it is, you'll get the problem I describe in the thread I sent you.

 

[irenavassilia]

Everything's ok now, I figured out I was using a dll that was not usable or even needed for the program.
Thanks for the help guys.

Regards,

Irena

 

[BobRodes]

So, removing unused references from your program is the first step in building a package.

Let me also suggest that using a package allows you to create a user installable disk for your program. While it is a good thing to want to understand what's going on during an installation (dependent files, registering libraries, and the like), it's also a good thing to automate steps where possible. After all, if it weren't, we wouldn't be writing these computer programs in the first place!

Glad you got it working.

Bob