I recently released the latest version of one of my programs after testing it on numerous PC's.
But upon release to some 80 users, 3 get an "Unexpected Error" messagebox followed by the program stopping at startup. I copied the program to a new project and systematically cut it back and cut it back until I get the minimum program which will run on my PC but not on theirs....
Private Sub Form_Load()
Dim frmDataForm As New DataGridForm
frmDataForm.Visible = True
End Sub
DataGrid form is a form with an MSFLEXGRD on it (and nothing else). I have removed all other components which are not required in this test.
I have checked the version of MSFLEXGRD.ocx on a number of PC's and though there are two different versions on the 80 PC's, there is no correlation with working/not working status. I have also copied an independant version of the component and un-registered and then re-registered the component on a "bad" PC without luck. I also know that "bad" PC's will run other Visual Basic programs without problems - although none have MSFLEXGRD. All PC's are Windows XP and I use VB6 only.
I did consider reinstalling Visual Basic run time files on a "bad" PC but this is more in desperation than logic.
Any ideas ?
But upon release to some 80 users, 3 get an "Unexpected Error" messagebox followed by the program stopping at startup. I copied the program to a new project and systematically cut it back and cut it back until I get the minimum program which will run on my PC but not on theirs....
Private Sub Form_Load()
Dim frmDataForm As New DataGridForm
frmDataForm.Visible = True
End Sub
DataGrid form is a form with an MSFLEXGRD on it (and nothing else). I have removed all other components which are not required in this test.
I have checked the version of MSFLEXGRD.ocx on a number of PC's and though there are two different versions on the 80 PC's, there is no correlation with working/not working status. I have also copied an independant version of the component and un-registered and then re-registered the component on a "bad" PC without luck. I also know that "bad" PC's will run other Visual Basic programs without problems - although none have MSFLEXGRD. All PC's are Windows XP and I use VB6 only.
I did consider reinstalling Visual Basic run time files on a "bad" PC but this is more in desperation than logic.
Any ideas ?