edward_ce
November 16th, 1999, 11:39 AM
This is in reference to Mr. Chris Eastwood's reply to the post "A problem with GUID??!!" dated Nov. 12, 1999.
As enumerated in his recommended procedure to solve this problem, he stated in Step # 3 this: "go to Project->Components and uncheck the missing reference. Add in the new version of your component."
I couldn't find a MISSING message in the Project->Components dialog. But my OCX is listed although it is not selected (no check mark). I did the following steps:
1. Load the project group and ignore the error messages
2. Compile OCX project using NO COMPATIBILITY option
3. Save the OCX project and quit VB6 IDE.
4. Load VB6 and open the project group.
5. Highlight the main project (not the OCX project) from Project Explorer.
6. Go to Project->Components then check the OCX
7. Save the main project.
8. Quit VB6 IDE.
And behold! The next time I reloaded my project in the VB6 IDE, all the references were perfectly in place - no form loading errors appeared anymore. I got my senses back again.
But when I tried to compile the main project, the same problem came up. I keep on getting the same compilation error as before: "Method or data member not found". The error points at an instance of the custom control.
When I press SHIFT-F2 (go to definition) while the cursor was positioned in the wayward instance of the custom control, I get the following error message:
"Cannot jump to ctlXXX because it is hidden"
It was then when I noticed that all instances of the custom control in the form were dimmed (or grayed out). And horror of horrors! After thorough scrutiny I found out that the instance of my custom controls were all redefined as PictureBox. What a great miracle (or could it be Microsoft magic?).
Magic or no magic, that would sure make you scream. (I'm sure I didn't accidentally make the redefinition of the controls myself - not even during my fit of temporary insanity, LOL!).
Anyways, I did solve the problem in no time at all. I got the backup copy. What a brilliant solution, isn't it?
If I never had the backup, how can I put those unwanted PictureBox controls back to their original definitions (and glory)? Please, don't tell me that I have to create the form again.
Is there a way to get back the original control definitions?
As enumerated in his recommended procedure to solve this problem, he stated in Step # 3 this: "go to Project->Components and uncheck the missing reference. Add in the new version of your component."
I couldn't find a MISSING message in the Project->Components dialog. But my OCX is listed although it is not selected (no check mark). I did the following steps:
1. Load the project group and ignore the error messages
2. Compile OCX project using NO COMPATIBILITY option
3. Save the OCX project and quit VB6 IDE.
4. Load VB6 and open the project group.
5. Highlight the main project (not the OCX project) from Project Explorer.
6. Go to Project->Components then check the OCX
7. Save the main project.
8. Quit VB6 IDE.
And behold! The next time I reloaded my project in the VB6 IDE, all the references were perfectly in place - no form loading errors appeared anymore. I got my senses back again.
But when I tried to compile the main project, the same problem came up. I keep on getting the same compilation error as before: "Method or data member not found". The error points at an instance of the custom control.
When I press SHIFT-F2 (go to definition) while the cursor was positioned in the wayward instance of the custom control, I get the following error message:
"Cannot jump to ctlXXX because it is hidden"
It was then when I noticed that all instances of the custom control in the form were dimmed (or grayed out). And horror of horrors! After thorough scrutiny I found out that the instance of my custom controls were all redefined as PictureBox. What a great miracle (or could it be Microsoft magic?).
Magic or no magic, that would sure make you scream. (I'm sure I didn't accidentally make the redefinition of the controls myself - not even during my fit of temporary insanity, LOL!).
Anyways, I did solve the problem in no time at all. I got the backup copy. What a brilliant solution, isn't it?
If I never had the backup, how can I put those unwanted PictureBox controls back to their original definitions (and glory)? Please, don't tell me that I have to create the form again.
Is there a way to get back the original control definitions?