Pro VB 6For advanced Visual Basic coders working in version 6 (not .NET). Beginning-level questions will be redirected to other forums, including Beginning VB 6.
Welcome to the p2p.wrox.com Forums.
You are currently viewing the Pro VB 6 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
Microsoft Windows Common Controls 5.0 (SP2) [COMCTL32.OCX]
Microsoft Windows Common Controls 2 5.0 (SP2) [COMCT232.OCX]
Microsoft Windows Common Controls 6.0 (SP4) [MSCOMCTL.OCX]
Microsoft Windows Common Controls 2 6.0 (SP6) [MSCOMCT2.OCX]
Microsoft Windows Common Controls 3 6.0 (SP5) [COMCT332.OCX]
I just got a new computer, and I loaded VB6 Enterprise, and SP4.
But even before getting the new machine, I had the problem descxribed below.
Though I have these libraries, when I try to add them to a project, permission is denied.
An .exe I created back when I could add these libraries runs properly, and uses the controls found in one or more of these libraries (including an image list, a toolbar and a slider).
I really would like to regain access to these libraries for design time.
How did MS distribute these libraries? What package were they in? Suggestions?
================================================== =========
Read this if you want to know how to get a correct reply for your question.
(Took that from Doug signature and he Took that from Peter profile)
================================================== =========
My programs achieved a new certification : WORKS ON MY MACHINE
================================================== =========
I know that CVS was evil, and now i got the proof.
================================================== =========
Nope.
The previous machine exhibiting this problem (a machine which had worked for design time, but later did not) had Windows 2000.
Current machine has Windows XP Professional, SP2.
Last edited by BrianWren; January 29th, 2009 at 11:43 AM..
Nope.
The previous machine exhibiting this problem (a machine which had worked for design time, but later did not) had Windows 2000.
Current machine has Windows XP Professional, SP2.
Although I dont think that the problem is caused by the user privilege you have, but it is worth a try anyways... Check what windows user you are using to log in to windows... You may need to login as an administrator...
MS Windows Common Controls
