Printable View
I am trying to publish an application for network (NT) workstations. It works ok on my machine, but I am having trouble getting it to work elsewhere. I've tried copying dll's as specified in boot errors, and am now getting an error "ActiveX component cannot create objects" from my MDI. Is there an easy way to specify what files are missing, or do I just keep copying files until I get the right one?
I used the P/D wizard and that did round up the .dlls for me, thanks. But I'm still getting and Error 429 - "ActiveX components can't create object" on the workstation when I try to start.
Can you tell me more about registering components? I am unfamiliar with this procedure?
When you invoke a method on an object, windows searches in the registry for the class name/CLSID to be able to instantiate that object. If it cannot find the name of the component in the registry, then it gives you that error. When you run REGSVR32.EXE DLLNAME.DLL, the registry entries are added and the next time that a method is invoked on an object, windows will be able to find the DLL and load it accordingly.
That may or may not make sense to you, but COM is a somewhat complicated animal.
Anyways, what is your code doing that gives you that error at that point in time?
What files are you distributing? Why are you not using the Package/Deploy Wizard? Are you registering the components after you copy them to you clients workstations? (Ex. regsvr32.exe mylib.dll)
It is difficult to say what creates the error at that point. It is loading a MDI with many forms and controls and, of course, it doesn't create an error in p-code where I can debug it.
I had the idea that setup.lst gave instructions for the support files to self-register. Is there some files that do not self-register, and how can I tell them apart?
Come to think about it - the error occurs at the beginning of the load, something in the .bas or possibly my database connectstring. Is it possible this error occurs because of the database connection?
Possibly --- If you are attempting to connect to a database, you need to use DAO or ADO files to connect....
Does your project use ADO or DAO? Are these files included in your setup package?
That appears to be it, it bombs just as I'm making my database connection. I added a bunch of .dlls for my ADO connection - using msjetoledb40, and included the .dlls setup asked for on installation: ie., msjint40, msjter40, and mswstr10. And still it bombs (err msg 429 mentioned above).
Can you think of anything else I need to make the connection?
Assuming you are using ADO, you have to download and run the MDAC setup on the client (from M$ -- http://www.microsoft.com/data), you can't just throw DLL files in the users' SYSTEM directory as you please and expect them to work....
:)
That's the missing link! hey thanks clunietp - if that is your real name.
Tom is my real name. Is your real name okdorje?