Hi there,
We have a rather large VB6 system that needs to be "tweaked" to run on windows 7 machines. Have managed to run the project in the IDE and have successfully compiled and run the system. However, there are certain screens that are simply freezing.
What is strange though is that I get the compile error - "Variable not defined" - occurring seemingly at random
For example, say I have project Project.vbp with a class ExampleClass.cls then previously under XP there was no need to include the Object name in a variable declaration
Eg.
dim objExampleClass as new ExampleClass
rather than
dim objExampleClass as new Project.ExampleClass
Now this is usually a fairly common and easily fixable error but what is strange is that it doesn't happen all the time. Sometimes it all compiles fine and runs, but other times these compile errors occur.
For example, it was happening just before lunchtime, I went for lunch, and when I returned it compiled fine - and I hadnt even closed or re-loaded the IDE !!
The obvious (and painstaking) solution is to keep compiling and adding the object references where missing but there are millions of lines of code and I can't help thinking this is just a symptom of a deeper problem within Windows 7...
I am working in a project group consisting of 25+ projects and I have opened and compiled each project individually with no problems so there doesn't appear to be a problem with incorrect/missing references....
Anyone any ideas ?? Any help would me MUCH appreciated....
We have a rather large VB6 system that needs to be "tweaked" to run on windows 7 machines. Have managed to run the project in the IDE and have successfully compiled and run the system. However, there are certain screens that are simply freezing.
What is strange though is that I get the compile error - "Variable not defined" - occurring seemingly at random
For example, say I have project Project.vbp with a class ExampleClass.cls then previously under XP there was no need to include the Object name in a variable declaration
Eg.
dim objExampleClass as new ExampleClass
rather than
dim objExampleClass as new Project.ExampleClass
Now this is usually a fairly common and easily fixable error but what is strange is that it doesn't happen all the time. Sometimes it all compiles fine and runs, but other times these compile errors occur.
For example, it was happening just before lunchtime, I went for lunch, and when I returned it compiled fine - and I hadnt even closed or re-loaded the IDE !!
The obvious (and painstaking) solution is to keep compiling and adding the object references where missing but there are millions of lines of code and I can't help thinking this is just a symptom of a deeper problem within Windows 7...
I am working in a project group consisting of 25+ projects and I have opened and compiled each project individually with no problems so there doesn't appear to be a problem with incorrect/missing references....
Anyone any ideas ?? Any help would me MUCH appreciated....