cdv
asked on
Compiled program wont run on Windows 2000
I have written a very simple routine in VB6 and compiled it on a Windows 98 machine. This program works perfectly on 95/98 and NT machines. It will not run on any 2000 machine. The error message is Error number 429 - ActiveX component can't create object.
A clue is that if you load Office 97 on the 2000 machine the program runs perfectly even if you then unload Office again.
Clearly something is missing in the basic system and this is loaded when installing Office 97 - problem is what?
Any ideas?
A clue is that if you load Office 97 on the 2000 machine the program runs perfectly even if you then unload Office again.
Clearly something is missing in the basic system and this is loaded when installing Office 97 - problem is what?
Any ideas?
Hi!
Another method would be to copy the ocx component that you're using and dump it into the same folder as your app or dump that ocx to the "C:\Windows\System" folder.
That's it!
glass cookie : )
Another method would be to copy the ocx component that you're using and dump it into the same folder as your app or dump that ocx to the "C:\Windows\System" folder.
That's it!
glass cookie : )
ASKER
Timcottee
1) No it does not relate to my previous question.
2) I did use the P&D wizard to create the install files and this was used to load the software on the target machine.
Glass Cookie
This may solve the problem - but it is not addressing the cause i.e. why does it not work automatically. If it was a complex program there would be many OCX's to load. The error message does not tell you what is missing. It could be quite a mission to find out which is the missing component.
1) No it does not relate to my previous question.
2) I did use the P&D wizard to create the install files and this was used to load the software on the target machine.
Glass Cookie
This may solve the problem - but it is not addressing the cause i.e. why does it not work automatically. If it was a complex program there would be many OCX's to load. The error message does not tell you what is missing. It could be quite a mission to find out which is the missing component.
what does your program do? what refferences? what ocxs?
Hi!
I suppose it's because that PC doesn't have Office or whatever office component that you use. That's why after installing a MS Office application, the ocx files are also installed and registered on the PC. Uninstalling Office or whatever office application after that wouldn't cause the ocx files to be removed.
That's it!
glass cookie : )
I suppose it's because that PC doesn't have Office or whatever office component that you use. That's why after installing a MS Office application, the ocx files are also installed and registered on the PC. Uninstalling Office or whatever office application after that wouldn't cause the ocx files to be removed.
That's it!
glass cookie : )
Does the set up process raise any error message -unable to register ...?
Install DevStudio into the w2k computer na d have a close look at your code to determine the real problem.
Install DevStudio into the w2k computer na d have a close look at your code to determine the real problem.
Hi cdv,
How's your problem? : )
That's it!
glass cookie ; )
How's your problem? : )
That's it!
glass cookie ; )
ASKER
Sorry to not have responded yet. I have been out of the country and am about to leave again. It will be some time before I can investigate this problem any further.
Many thanks - you will need to wait until I get some time. :)
Many thanks - you will need to wait until I get some time. :)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
tried resrv32 on the target machine?
ASKER
I did not solve this problem. However I have done a complete rebuild of the development machine and this seems to have corrected the problem. It seems there may have been a corruption of some sort.
Sorry about the long delay - but I put off the rebuild for a long time.
Sorry about the long delay - but I put off the rebuild for a long time.
Anyway I would guess that you have not used the p&d wizard to install the package on the target machine. If you simply copy the executable then the necessary components may not be installed and registered.