Folks,
I have an application which uses an in-house developed ActiveX control. On most machines it works fine, but some users get a runtime error 372 or sometimes 374 indicating that the thing was not loaded, version may be incorrect, etc. There is only one version and it works for most users, only once in a while I get a user with this problem.
Of course the main question is, what could be causing this?
I also ask a little guidance, how could I enhance the code so I don't have to post here to get help? I'd really like to put something into the code to find out exactly what's going on. I actually inherited this code from someone, but I dont see where there is anything explicitly invoking the control, it was just dragged and dropped onto the main form. How can I determine what's going on? I understand that the control should self-register, so looking at the registry is no help.
Also, at least one of these users is using a Service Pack 1 greater than what we specify for the application. This again is a more general question - how does one in general write VB apps such that the customer cannot break it by loading a new SP which he needs for some other app on his PC?
Thanks much
I have an application which uses an in-house developed ActiveX control. On most machines it works fine, but some users get a runtime error 372 or sometimes 374 indicating that the thing was not loaded, version may be incorrect, etc. There is only one version and it works for most users, only once in a while I get a user with this problem.
Of course the main question is, what could be causing this?
I also ask a little guidance, how could I enhance the code so I don't have to post here to get help? I'd really like to put something into the code to find out exactly what's going on. I actually inherited this code from someone, but I dont see where there is anything explicitly invoking the control, it was just dragged and dropped onto the main form. How can I determine what's going on? I understand that the control should self-register, so looking at the registry is no help.
Also, at least one of these users is using a Service Pack 1 greater than what we specify for the application. This again is a more general question - how does one in general write VB apps such that the customer cannot break it by loading a new SP which he needs for some other app on his PC?
Thanks much
