-
I am getting this message when I install my program on Windows 95 machines. It does not seem to be a problem when I install them on '98 machines.. My program uses database connectivity (DAO), so MDAC_TYP.EXE has been included when packaged with the P&DW. When running the install for my program, everytthing completes with no error messages. However, when i go to run my program i get that "ActiveX cannot create object message". I've tried several things. I tried downloading DCOM95 and installing it along with the newest version of MDAC_TYP to no avail..
Any ideas, anyone??
-jman
-
I hope, this may be the problem,
I think, U hv used an an ActiveX component (which is not an intrinsic control) and u might missed to add that file as a dependency file when u are creating setup program using P & D wizard.
Pls. register that activex ocx or dll, .exe file in u'r client m/c and run the application....
Luv,
Md. Rafik. B.
[email protected]
-
You usually get this error when you have not registered an activex control or dll properly. Use regsvr3s.exe found sometimes in the windows system direcoty, drag the activex/dll over this and let go to register it
-
same error again
Ok, I've looked at the activeX controls.. and why does it work fine on windows 98 systems? Only on the older 95 systems do i run into trouble with that activex error message. I'll keep checking.. any other ideas?
-jman
-
What active x control is this and for what app
-
This is not that complex a program... The only activeX controls i am using are the common dialog box and the DBList control.. I am also using the Data Control, but I believe that is an intrinsic control. All the program does is use the data control to connect to a database, displays a record from the database. I spent practically all day yesterday trying to figure this one out to no avail.. It looks like i'm going to get installshield and try that next. I'll let you guys know how that worked. I appreciate all the help.
still puzzled,
-jman
-
Ok, problem solved.
Thanks guys for your help, I figured it out.. The problem was my program was using the FSO object and there was no reference to the Microsoft Scripting Runtime.. SO the program needed SCRRUN.DLL which was not included by the Package and Deployment wizard... I also obtained installshield--and it is way better than the PDW.
