07-19-2002, 08:29 AM
While using Install Setup Wizard, I was prompt by such a note.
The dependecy file for the following components is out of date
and it listed OCXs:
What does it mean, Won't my aplliation and it's setup work corectly. How can solute this problem. This wizard says something about rebuilding those dependency files by this wizar. Heee....? I don't get it
07-19-2002, 08:52 AM
i could be wrong, but what i think happened here is that you installed a program previously that overwrote those OCX's with older or corrupt versions. then again, it could be a date error in your hard drives FAT (file allocation table). try running scandisk first, and if that doesnt work, you might want to try downloading the VB runtime files from the microsoft site to replace those OCX's.
07-19-2002, 09:38 AM
There are several solutions for this on the M$ website, try searching at http://msdn.microsoft.com
07-19-2002, 10:15 AM
I can't fix it...
anyway what does those dependency files do? are they so important?
07-19-2002, 10:26 AM
Urr, yes. ComCtl is the common controls library and comdlg is the common dialog control.
07-20-2002, 03:07 AM
What does it mean they are out of date? They are to old or what?
My setup will copy them at user's machine, so they will work, won't they?
07-20-2002, 04:10 AM
Is your machine running the latest service pack?
07-20-2002, 04:12 AM
no it isn't, so probably it's the biggest problem...
07-21-2002, 06:00 PM
come on guys, help me...
I still did not solve this #%&^$#@# problem with this out of date thing. I've search the web for some information, I've install those controls again, I've reinstall my windows and nothing helps.
07-21-2002, 06:21 PM
I wouldn't worry about the message. It is saying that it can't
accurately determine what other files these two OCX files are
dependent on. I think every dependency they have should
already be a part of windows. Now if you run the program after
the install and one or both of these controls causes an error, then
there would be something to worry about.
07-21-2002, 07:08 PM
hm..... I haven't already install it on other then my machine, but on mine it works perfect.
07-25-2002, 07:48 AM
I would definatly be trying to run that program on other machines. Your computer is already setup with VB, which means all VB runtimes are installed. I recently released an application which ran perfect on my computers. Come to find out later on that the only reason is ran perfect on my computers is that I had VB installed on all of them. If you want to test your app properly you need to try and install it on a computer which has a clean install of windows. (NO OTHER PROGRAMS SHOULD BE INSTALLED) Once you can try your install on a clean machine you will instantly know if your setup has a problem, or if its just some random error caused by your machine only. Never release anything unless you can test its setup on a computer with nothing installed but windows. Then you'll be almost 100 percent sure that it will work. Hope this helps.
07-25-2002, 10:18 AM
I normally find that Win95 serves very well for that purpose. I actually have an installer test box that has it its harddrive duplicated in a hidden partition. you can then just restore the hidden partition to start again with a completely clean windows.
I use Win95 because it really is about as un-adourned as its possible to get with Windows. However, you should be careful to check it on an NT box too since some files and functions differ between the two platforms.