Solved: Package and Deployment with VB6

Create Account

Visual Basic Classic

Questions

Followers

Top Experts

LoveToProgram

Package and Deployment with VB6

I am currently having an incredible amount of difficulty packaging a propram up that I have devoloped using VB6. When I install in on any other computer besides the computer that the program was devoloped on I get the message:

Run-time error- 2147221164(80040154)'

Class not registered.

I am assuming that somthing is not registering in the registry the way that it should. I built a class in this program that has a .cls extension. Is there somthing that I need to do with this class to register it on the users computer? The other thing is that I am useing the TRue DBGRID 6.0 and am sending out the necessary files that this control requires. But am still geting this message. Any idea's.

Zero AI Policy

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.

vettranger

If you haven't downloaded and installed SP3 for VB6, that is the first place to start. It fixed an incredible number of bugs in the PDW. My information straight from a top VB rep at Microsoft is that SP3 took the PDW from unusable to pretty darn usable. ;-)

ASKER CERTIFIED SOLUTION

AnswerTheMan

membership

Signing up is free and takes 30 seconds. No credit card required.

Create Account

CArnold

Ahh, yes. Don't you love how Microsoft can create oxymorons out of simple words? Like "Wizard"?

I've just recently had several problems with using the Setup Wizard, myself. Perhaps some of the solutions I've discovered will help you with problem.

-If installing to a Win95/98 machine, install DCOM95/DCOM98 onto the target system prior to running your setup file.

-Comb your SETUP.LST file for any anomolies. For instance, there is a bug with the Calendar control: when preparing the Setup.lst, the setup Wizard will throw in an unneccessary "EX" behind the DLLSelfRegisterCommand, making the syntax appear "$(DLLSelfRegisterEX)". By simply removing the "EX", the DLL was able to register properly.

-Make sure that the version numbers reported in your SETUP.LST are correct.

-You should not have to do anything "special" with projects containing class modules. The PDW is pretty efficient at determining dependency files and including them with your package.

AnswerTheMan

CArnold : oxymorons ??? :)))))))
Try InstallShield for VisualC++ 6.0 to create a setup for a project, and then
you'll fall inlove with VB deploiment wizard...........
Regarding the Calander control - that's an old problem from VB5. now, in Vb6 sp3
i see a new version (9) of this control (or did it came from Office2000 i've just installed ??).
regarding DCOM - if IE4.01(at least) is on the machine - you don't need that.

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.

LoveToProgram

ASKER

AnswerTheMan you did it and in record time. It was unbeleivable that you got back with a answer as quick as you did, (and A correct one at that) but I guess that is why they call you AnswerTheMan.

Thanks

Mirkwood

Bought This Question.

Visual Basic Classic

Questions

Followers

Top Experts

Visual Basic is Microsoft’s event-driven programming language and integrated development environment (IDE) for its Component Object Model (COM) programming model. It is relatively easy to learn and use because of its graphical development features and BASIC heritage. It has been replaced with VB.NET, and is very similar to VBA (Visual Basic for Applications), the programming language for the Microsoft Office product line.