Hello all,
OK, this is so weird that I am wondering whether it's a bug in VB6....
I am using a custom made application for my job that I can change at will and that has grown pretty big. Recently, I wanted to add a routine that could read excel files. However, whenever I try to add the Reference to the MS Excel 9.0 library, I cannot run the program anymore because VB suddenly reports a "type mismatch" error in the following routine:
Sub AskForBut()
Dim buttt As Button
For Each buttt In ToolToggle.Buttons
If buttt.Value = tbrPressed Then MakeTree buttt.Key: Exit For
Next buttt
End Sub
But these things have nothing to do with one another! How can there suddenly be an error when before things were fine, only because I added a reference?!
Is it a question of homonymy with some variables/functions in the Excel library?
OK, this is so weird that I am wondering whether it's a bug in VB6....
I am using a custom made application for my job that I can change at will and that has grown pretty big. Recently, I wanted to add a routine that could read excel files. However, whenever I try to add the Reference to the MS Excel 9.0 library, I cannot run the program anymore because VB suddenly reports a "type mismatch" error in the following routine:
Sub AskForBut()
Dim buttt As Button
For Each buttt In ToolToggle.Buttons
If buttt.Value = tbrPressed Then MakeTree buttt.Key: Exit For
Next buttt
End Sub
But these things have nothing to do with one another! How can there suddenly be an error when before things were fine, only because I added a reference?!
Is it a question of homonymy with some variables/functions in the Excel library?