429 ActiveX component can't create object

I've compiled an application which is linked to an access database.  As far as I can tell I have copied all of the dll's, ocx's etc (the setup program was crashing all the time - hence the manual copying) but I still get the error "Run-time error 429.  ActiveX component can't create object".

Technet says that this may be an NT4 issue with long filenames but I have shortened the file names to no avail.  Besides, I get the same error on a 95 machine.  

Any ideas would be greatly received as I don't get paid until it works!!
Luke_StephensAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

paul_tsekovCommented:
Hi VBFan,
  The VB6 Package and Deployment Wizard is BUGGY.
   Almost noone uses it anymore.

So go here:
http://msdn.microsoft.com/vstudio/downloads/vsi/default.asp

 From here you can download Visual Studio Installer 1.0

  It solves all the problems with creating SETUP packages.
  So it works almost like the Package and Deployment Wizard but for SURE
it isn't BUGGY.

   Try it!

      Pavel Tsekov
   email : paul_tsekov@yahoo.com
0
Luke_StephensAuthor Commented:
I'll download it and test it.  If it works the points are all yours mate.

Cheers
0
Éric MoreauSenior .Net ConsultantCommented:
When installing on an NT computer, you have to be logged as Administrator. Did you?

Also, SP3 of VB6 correct a lot problem in PDW. Did you installed it?

I have installed a lot of applications using VB6-PDW without much problems!
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

Luke_StephensAuthor Commented:
No I wasn't logged on as an administrator on NT4, but I've had the same problem on a win95 machine where I was.

I'm currently downloading the SP3 so I shall let you know whether it works or not.

Cheers,

Luke
0
SnipeCommented:
Hi!
If your application links to database you should include in installation "Microsoft Data Access Components" (Mdac_typ.exe file). You can find it on Microsoft Visual Studio Disk in \COMMON\IDE\IDE98\REDIST directory or download from site http://www.microsoft.com/data/download.htm. This is separate installation file which contains all necessary components for accessing to database.  I have the similar error when use ADO and correct it after MDAC installation.
If you use Package and Deployment Wizard the possible reason for installation craching is non-American date format on your system. If so, you should manually edit file setup.lst and change all dates on "mm/dd/yy" or "mm/dd/yyyy" format - setup1.exe understands dates only in this format!
0
SnipeCommented:
Hi!
If your application links to database you should include in installation "Microsoft Data Access Components" (Mdac_typ.exe file). You can find it on Microsoft Visual Studio Disk in \COMMON\IDE\IDE98\REDIST directory or download from site http://www.microsoft.com/data/download.htm. This is separate installation file which contains all necessary components for accessing to database.  I have the similar error when use ADO and correct it after MDAC installation.
If you use Package and Deployment Wizard the possible reason for installation craching is non-American date format on your system. If so, you should manually edit file setup.lst and change all dates on "mm/dd/yy" or "mm/dd/yyyy" format - setup1.exe understands dates only in this format!
0
Luke_StephensAuthor Commented:
Right,

I've now installed SP3, MDAC_typ.exe, and the installation program update and I'm getting the following error:

'The file 'C:\Windows\Temp\msftqws.pdw\$(DLLSelfRegisterEx)' could not be registered because it could not be found.'

This file doesn't exist in my temp directory, and creating it doesn't help either.  

I'm pretty sure I got this error before updating all of the above as well.

Somebody help me or this keyboard is going to get destroyed like the last one!!

Cheers,

Luke
0
Éric MoreauSenior .Net ConsultantCommented:
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
SnipeCommented:
Try to find and remove any reference on file msftqws.pdw in setup.lst
0
Luke_StephensAuthor Commented:
Is there any way to share the points?  Several answers contributed to the fixing of this problem so I feel bad about giving all the points to one person!
0
Éric MoreauSenior .Net ConsultantCommented:
You can post new dummy questions that will look like "for «expert-name».
0
Luke_StephensAuthor Commented:
I haven't got the time to do that.  You have them emoreau, I think that it was your answer that did it.
0
Luke_StephensAuthor Commented:
Sorry mate, still got the same errors, someone else came up trumps though.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.