VB Controls, COMCTL32.OCX and COMDLG32.OCX problems.

COMCTL32.OCX and COMDLG32.OCX problems.

Author	Message
Joakim Sch?dstr? #1 / 6	COMCTL32.OCX and COMDLG32.OCX problems. Hi ! After having installed, the VB5cce the COMCTL32.OCX and COMDLG32.OCX can not be registered when distributing VB4-programs. This problem occurs if neither the VB5cce nor the msie301m95 have been installed on the client.
Sat, 26 Jun 1999 03:00:00 GMT

Warren Swai #2 / 6	COMCTL32.OCX and COMDLG32.OCX problems. On Tue, 07 Jan 1997 11:57:58 -0800, "Joakim Sch?dstr?m" Quote: >Hi ! >After having installed, the VB5cce the COMCTL32.OCX and COMDLG32.OCX can >not be registered when distributing VB4-programs. This problem occurs if >neither the VB5cce nor the msie301m95 have been installed on the client. The node object in the VB5.0 COMCTL32.OCX does not support the .tag property. Little did I know when I recompiled my VB4.0 app that this little larve would be waiting to hatch. I'd like to call it a bug, but no doubt Microsoft have got it covered in the small print somewhere. The opinions expressed here are not necessarily those of the author.
Sun, 27 Jun 1999 03:00:00 GMT

RAM #3 / 6	COMCTL32.OCX and COMDLG32.OCX problems. That's because the new OCX's have new dependencies. I don't know what they are but you may try to distribute the COMCTL32.DLL and the COMDLG32.DLL files also. Good luck. You could always get the old OCX's from your VB4 installation and VB5 can use them just fine. Then you wouldn't have this problem. Quote: > Hi ! > After having installed, the VB5cce the COMCTL32.OCX and COMDLG32.OCX can > not be registered when distributing VB4-programs. This problem occurs if > neither the VB5cce nor the msie301m95 have been installed on the client.
Thu, 01 Jul 1999 03:00:00 GMT

Rob Graha #4 / 6	COMCTL32.OCX and COMDLG32.OCX problems. It would appear that you need to install asycfilt.dll,stdole2.tlb,and oleaut32.dll (in that order, and register al least oleaut32.dll. oleaut32 seems to take care of registering stdole2.tlb). Figured this out partly by looking at the comctl32.dep file and by trial and error. :-) rob Quote: > Hi ! > After having installed, the VB5cce the COMCTL32.OCX and COMDLG32.OCX can > not be registered when distributing VB4-programs. This problem occurs if > neither the VB5cce nor the msie301m95 have been installed on the client.
Fri, 02 Jul 1999 03:00:00 GMT

Vlajko Knezi #5 / 6	COMCTL32.OCX and COMDLG32.OCX problems. Quote: > That's because the new OCX's have new dependencies. I don't know what they > are but you may try to distribute the COMCTL32.DLL and the COMDLG32.DLL > files also. > Good luck. You could always get the old OCX's from your VB4 installation > and VB5 can use them just fine. Then you wouldn't have this problem. Problem is that eather COMCTL32.DLL or COMDLG32.DLL can not be overwritten while Windows95 is running. You can ask user to reboot PC in DOS mode, copy the file and than start Setup again. Is there any other alternative? Vlajko Knezic
Sun, 11 Jul 1999 03:00:00 GMT

Rob Graha #6 / 6	COMCTL32.OCX and COMDLG32.OCX problems. The new dependancies are in OLE2.2 (which is installed by MSIE3.0...) the required files are Asycfilt.dll stdole2.tlb oleaut32.dll (self register) Regards, Rob Graham Quote: > That's because the new OCX's have new dependencies. I don't know what they > are but you may try to distribute the COMCTL32.DLL and the COMDLG32.DLL > files also. > Good luck. You could always get the old OCX's from your VB4 installation > and VB5 can use them just fine. Then you wouldn't have this problem. > > Hi ! > > After having installed, the VB5cce the COMCTL32.OCX and COMDLG32.OCX can > > not be registered when distributing VB4-programs. This problem occurs if > > neither the VB5cce nor the msie301m95 have been installed on the client.
Mon, 12 Jul 1999 03:00:00 GMT

Page 1 of 1

[ 6 post ]