Hi all.
I was in the process of packaging/deploying a vb6 program and ran into a head scratcher. I gave up on the vb6 Package & Deployment Wizard (A better name would be Package & Deployment Moron :))) and use Inno Setup instead. What is happening is I can install the program on my Win7 system, and two Win XP laptops, but not on another Win7 laptop. I get the Runtime Error 380: Invalid property value error after the program is installed and then run. This error came up originally in response to a font that was not installed, so I fixed that quickly enough, but the other Win7 laptop just will not cooperate. So, I put a bunch of 'debug' points throughout the form_load procedure where I narrowed the problem down to, that do nothing more than print lines out to a txt file when certain points in the procedure are completed successfully. The area where the crash occurs is highlighted below:
I know that MS states that one thing that can cause the error is a hidden control on a form. But they also state this was a problem in vb5 and earlier, not vb6. AND my control (Locale_frame) is NOT hidden.
I have many questions:
1. Why would such an insignificant set of lines cause such havoc?
2. Or is it possible that something else is going on that just happens to trigger right when those lines are reached?
3. Or, could this be something I am not doing in the Inno script? If that is the case, why would Inno fail on only one machine?
4. Could some Win7 systems have a problem with the vb6 frame control?
As always, your advice is greatly appreciated!
I was in the process of packaging/deploying a vb6 program and ran into a head scratcher. I gave up on the vb6 Package & Deployment Wizard (A better name would be Package & Deployment Moron :))) and use Inno Setup instead. What is happening is I can install the program on my Win7 system, and two Win XP laptops, but not on another Win7 laptop. I get the Runtime Error 380: Invalid property value error after the program is installed and then run. This error came up originally in response to a font that was not installed, so I fixed that quickly enough, but the other Win7 laptop just will not cooperate. So, I put a bunch of 'debug' points throughout the form_load procedure where I narrowed the problem down to, that do nothing more than print lines out to a txt file when certain points in the procedure are completed successfully. The area where the crash occurs is highlighted below:
Code:
LogText_str = "MAIN_form form_load procedure point 6d4." + vbLf
Print #4, LogText_str
Drive2WriteStatus_label.Top = SeparatorLine.Y1 + 210
LogText_str = "MAIN_form form_load procedure point 6d5." + vbLf
Print #4, LogText_str
DestinationDirectory_label.Top = SeparatorLine.Y1 + 210
DestinationDirectory_label.Left = File1.Left + 15
LogText_str = "MAIN_form form_load procedure point 6d6." + vbLf
Print #4, LogText_str
Drive2.Width = CommonBoxesWidth
Drive2.Top = MainWin_TopGapDist + CommonBoxesHeight + MidArea_VGapDist
LogText_str = "MAIN_form form_load procedure point 6d7." + vbLf
Print #4, LogText_str
Locale_frame.Width = CommonBoxesWidth - 15
Locale_frame.Height = CommonBoxesHeight - LocaleFrame_DropDist
Locale_frame.Top = MainWin_TopGapDist + CommonBoxesHeight + MidArea_VGapDist + LocaleFrame_DropDist
LogText_str = "MAIN_form form_load procedure point 6d8." + vbLf
Print #4, LogText_str
Dir2.Width = CommonBoxesWidth
Dir2.Height = CommonBoxesHeight
Dir2.Top = MainWin_TopGapDist + CommonBoxesHeight + MidArea_VGapDist
Dir2.Left = File1.Left
LogText_str = "MAIN_form form_load procedure point 6e." + vbLf
Print #4, LogText_strI have many questions:
1. Why would such an insignificant set of lines cause such havoc?
2. Or is it possible that something else is going on that just happens to trigger right when those lines are reached?
3. Or, could this be something I am not doing in the Inno script? If that is the case, why would Inno fail on only one machine?
4. Could some Win7 systems have a problem with the vb6 frame control?
As always, your advice is greatly appreciated!