See my question OCX "Dependancy Question" for a complete history, which got quite lengthy. Recap:
Using VB5 (upgrade installed over VB3). Suddenly, the setup wizard started reporting that COMCTL32.OCX and COMDLG32.OCX had dependancy files that were out of date. VBGuru very kindly educated me.
Question #1: If these files were updated during my internet sessions, without my knowledge, and without updating the dependancy files, can I expect this to happen again from time to time? I am profoundly disturbed at that.
Following VBGuru's instructions, I downloaded VBSP3.EXE (took 2.5 hours!). Didn't know where to put it, and not wishing to clutter my desktop, I put in a file "norm". Executed it. It created two new subfiles under "norm".
"vs97_sp3" contains setup.exe, 10 subfolders with three letter names, and two .ico files.
Question #2: What is all that, and what should I do with it?
The other subfolder is named "v42", and I was astonished to see that it evidently contains a complete set of setup files for my application! I have three versions of my app, in different folders. Which one did it pick? Why? I could run those setup files and see. I would have expected that the service pack would fix the dependancy problem, and I would then create my setup files as usual.
Question #3: Should I delete all that stuff, move VBSP3.EXE to the folder where my VB5 lives, and then execute it?
Question #4: Exactly what is the proper procedure for using service packs?
I'm offering a lot of points for a careful tutorial covering these questions. I appreciate your help. -- Norm