If you download the update in your PC and extract the OCX files, I don't think it would be illegal to distribute them to your clients, and you could do it with a batch file that registers them, so it won't look that "unprofessional".
My PC doesn't have VB6 installed, I do all my work in Excel 2003 connected to a MySQL server.
I downloaded the VB6 update VB60SP6-KB957924-x86-ESN.EXE, then using 7-zip (any decent zipping app would do) opened the file as if it were a zip file, inside it there is a Product.CAB, extract it and...
I think that if you pull out the control(s) out of the VB6 update and then distribute them to your clients, maybe with an "install" procedure or batch or something, to automate the replacement of the "untrusted" control.
I faced this error after a rampage of the Conficker virus hit our company and the IT technicians left loose the controls on which updates got auto installed on our network.
What I did to solve it (I don't have VB6) was to download the VB6 update, open the EXE file with 7-zip and extracted...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.