Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.basic.visual.misc > #2031 > unrolled thread

Visual Basic 5

Back to article view | Back to comp.lang.basic.visual.misc

Contents

  Visual Basic 5 John Mott <johnmott@iinet.net.au> - 2014-04-25 16:21 +0800
    Re: Visual Basic 5 ralph <nt_consulting@yahoo.com> - 2014-04-25 07:46 -0500
      Re: Visual Basic 5 ralph <nt_consulting@yahoo.com> - 2014-04-25 10:47 -0500
        Re: Visual Basic 5 John Mott <johnmott@iinet.net.au> - 2014-04-26 10:43 +0800
          Re: Visual Basic 5 GS <gs@somewhere.net> - 2014-04-26 11:59 -0400
          Re: Visual Basic 5 ralph <nt_consulting@yahoo.com> - 2014-04-26 13:48 -0500
            Re: Visual Basic 5 John Mott <johnmott@iinet.net.au> - 2014-05-02 17:02 +0800
              Re: Visual Basic 5 Deanna Earley <dee.earley@icode.co.uk> - 2014-05-02 10:29 +0100
                Re: Visual Basic 5 John Mott <johnmott@iinet.net.au> - 2014-05-04 15:44 +0800
              Re: Visual Basic 5 GS <gs@somewhere.net> - 2014-05-02 14:21 -0400
              Re: Visual Basic 5 RW <RonW@no_domain.invalid> - 2014-05-02 15:27 -0400
                Re: Visual Basic 5 John Mott <johnmott@iinet.net.au> - 2014-05-04 15:48 +0800
                  Re: Visual Basic 5 ralph <nt_consulting@yahoo.com> - 2014-05-04 04:03 -0500
                    Re: Visual Basic 5 John Mott <johnmott@iinet.net.au> - 2014-05-08 17:30 +0800
                      Re: Visual Basic 5 John Mott <johnmott@iinet.net.au> - 2014-05-08 17:58 +0800
                      Re: Visual Basic 5 ralph <nt_consulting@yahoo.com> - 2014-05-08 08:52 -0500
                        Re: Visual Basic 5 ralph <nt_consulting@yahoo.com> - 2014-05-08 09:47 -0500
                          Re: Visual Basic 5 ralph <nt_consulting@yahoo.com> - 2014-05-08 11:38 -0500
                        Re: Visual Basic 5 RW <RonW@no_domain.invalid> - 2014-05-08 15:20 -0400
                          Re: Visual Basic 5 John Mott <johnmott@iinet.net.au> - 2014-05-09 15:32 +0800
                        Re: Visual Basic 5 John Mott <johnmott@iinet.net.au> - 2014-05-11 16:03 +0800
                          Re: Visual Basic 5 ralph <nt_consulting@yahoo.com> - 2014-05-11 11:29 -0500
                            Re: Visual Basic 5 GS <gs@somewhere.net> - 2014-05-11 14:28 -0400
                          Re: Visual Basic 5 ralph <nt_consulting@yahoo.com> - 2014-05-11 12:59 -0500
                          Re: Visual Basic 5 ralph <nt_consulting@yahoo.com> - 2014-05-11 14:04 -0500
                            Re: Visual Basic 5 ralph <nt_consulting@yahoo.com> - 2014-05-11 14:32 -0500
                            Re: Visual Basic 5 John Mott <johnmott@iinet.net.au> - 2014-05-12 16:49 +0800
                              Re: Visual Basic 5 ralph <nt_consulting@yahoo.com> - 2014-05-12 22:34 -0500
                                Re: Visual Basic 5 John Mott <johnmott@iinet.net.au> - 2014-05-13 14:51 +0800
                                  Re: Visual Basic 5 John Mott <johnmott@iinet.net.au> - 2014-05-13 17:12 +0800
                                    Re: Visual Basic 5 ralph <nt_consulting@yahoo.com> - 2014-05-13 08:01 -0500
                                      Re: Visual Basic 5 ralph <nt_consulting@yahoo.com> - 2014-05-13 09:36 -0500
                                        Re: Visual Basic 5 ralph <nt_consulting@yahoo.com> - 2014-05-13 09:43 -0500
                                        Re: Visual Basic 5 ralph <nt_consulting@yahoo.com> - 2014-05-13 09:55 -0500
                                        Re: Visual Basic 5 ralph <nt_consulting@yahoo.com> - 2014-05-13 10:16 -0500
                                        Re: Visual Basic 5 ralph <nt_consulting@yahoo.com> - 2014-05-13 13:24 -0500
                                          Re: Visual Basic 5 John Mott <johnmott@iinet.net.au> - 2014-05-14 17:30 +0800
                                            Re: Visual Basic 5 ralph <nt_consulting@yahoo.com> - 2014-05-14 07:05 -0500
                                              Re: Visual Basic 5 John Mott <johnmott@iinet.net.au> - 2014-05-15 16:58 +0800
                                                Re: Visual Basic 5 ralph <nt_consulting@yahoo.com> - 2014-05-15 07:37 -0500
                                                  Re: Visual Basic 5 John Mott <johnmott@iinet.net.au> - 2014-05-16 17:24 +0800
                                                    Re: Visual Basic 5 Deanna Earley <dee.earley@icode.co.uk> - 2014-05-16 13:58 +0100
                                                      Re: Visual Basic 5 John Mott <johnmott@iinet.net.au> - 2014-05-17 17:13 +0800
                                                        Re: Visual Basic 5 John Mott <johnmott@iinet.net.au> - 2014-05-18 16:05 +0800
                                                          Re: Visual Basic 5 ralph <nt_consulting@yahoo.com> - 2014-05-18 04:14 -0500
                                                            Re: Visual Basic 5 John Mott <johnmott@iinet.net.au> - 2014-05-19 17:28 +0800
                                                              Re: Visual Basic 5 Deanna Earley <dee.earley@icode.co.uk> - 2014-05-19 10:36 +0100
                                                                Re: Visual Basic 5 John Mott <johnmott@iinet.net.au> - 2014-05-20 16:32 +0800
                                                                  Re: Source control (Was: Visual Basic 5) Deanna Earley <dee.earley@icode.co.uk> - 2014-05-20 10:19 +0100
                                                                    Re: Source control (Was: Visual Basic 5) ralph <nt_consulting@yahoo.com> - 2014-05-20 11:59 -0500
                                                            Re: Visual Basic 5 John Mott <johnmott@iinet.net.au> - 2014-05-20 16:40 +0800
                                                        Re: Visual Basic 5 Deanna Earley <dee.earley@icode.co.uk> - 2014-05-19 08:55 +0100
                                            Re: Visual Basic 5 "Henning" <computer_hero@coldmail.com> - 2014-05-16 12:06 +0200
                  Re: Visual Basic 5 "Mayayana" <mayayana@invalid.nospam> - 2014-05-04 09:32 -0400
                  Re: Visual Basic 5 "Bill Skaggs" <eaglecrest@att.net> - 2014-05-04 06:34 -0700

Page 2 of 3 — ← Prev page 1 [2] 3  Next page →

#2078

On Thu, 08 May 2014 08:52:59 -0500, ralph <nt_consulting@yahoo.com>
wrote:

>On Thu, 08 May 2014 17:30:50 +0800, John Mott <johnmott@iinet.net.au>
>wrote:
>
>>Thank you Ralp
>>
>>I tried to execute your suggestion
>>
>>1. I do not have RegisterTLB.exe
>>
>>2. I found regtlibv12.exe in both
>>   c:\WINDOWS\Microsoft.Net\Framework\v4.0.30319 and
>>   c:\WINDOWS\Microsoft.Net\Framework64\v4.0.30319
>>
>>However I did not have success after running it.
>>I opened an elevated cmd prompt and changed to the \Windows\sysWOW64
>>folder and tried " reglibv12 comctl32.ocx" and it said it could not
>>find reglibv12. So Ichanged to
>>\WINDOWS\Microsoft.NET\Framework\v4.0.30319 and tried
>>" reglibv12 comctl32.ocx" and it said successful.
>>Unfortunately I still get comct32l.ocx not found errors when I try to
>>load source code or run the compiled exe file.
>>
>>I am not very experienced or knowledgable in system matters.
>>Any forther suggestions or can you tell me where I am going wrong ?
>>John
>>
>
>First off. My suggestion was narrowly focused on where to find a "Type
>Library Registration Tool" in order to follow-through with RW's
>suggestion to register the "msdatsrc.tlb" Type Library.
>
>[Frankly, I was not exactly sure why that would help outside the VBIDE
>- but I don't use VB5. <g>]
>
>To register COM components/controls (.dll, .ocx, ...) you will use
>regsvr32. The issue will be determining if the component is 32-bit or
>64-bit and thus which regsvr32 to use since Microsoft decided to give
>the same name to both. The following discussion pretty much hashes out
>all the nusances involved.
>
>http://stackoverflow.com/questions/4897685/how-do-i-register-a-dll-on-windows-7-64-bit
>
>It is good to check that everything is located on the target, properly
>registered, and to know how to fix registration issues should they
>come about, but not totally sure that is your real issue. Since all
>the components are there, the mismatch is coming from the fact your
>projects are compiled against one version and something else is what
>is available.
>
>Assumptions: 
>1) You have VB5 SP3 installed on your new platform (Win7 64-bit)
>2) You do not get errors when you open VB5
>3) But you do get errors when you attempt to open some projects
>That correct?


1) I have V5.0.37.24 installed on win7 64 bit

2) I do not get errors when opening VB5.

3) I do not get errrors opening a simple VB project but do get errors
trying to open a more complex project.

>
>Try this:
>Close the VBIDE.
>Open the  .vbp file of a troubled project in a text editor and delete
>the lines that reference comctl32.ocx and comdlg32.ocx. (Or any .oca
>reference that may have slipped in.)
>Save the file.
>Then open the project in VB, open project references, and add the
>common control components back. (Again, make sure you do not
>accidently select an '.oca'.)
>Save the changes to the vbp file and close.
>Re-open the project and test.
>
>Let us know the exact error/s you get, if any.
>
>-ralph

I used a text editor to delete lines refering to comctl32.ocx,
comdlg32.ocx and msflxgrd.ocx and the project then opened in VB but
showed error messages Error Loading refer to The numerous Frm.logs.
Log entries refer to invalid properties.
When I tied to run it I got I got compile error: 
user defined type not defined
Dim pn11 as Panel.

I then attempted to add the common control properties back in.
They showed as being referenced in the text file.
Succeeded with the three above mentioned ocx's, but I cannot fathom
how to add the Panel property back in.

When I try to run the project I get error message saying
cant add Panels - method or data member not found.

The various Frm logs are showing messages
Cannot load control sbar (name of form) ; license not found
and 
Line 122: Class MSComDlg.CommonDialog of control dlgCommonDialog was
not a loaded control class.
Line 125: The property name _ExtentX in dlgCommonDialog is invalid.
Line 126: The property name _ExtentY in dlgCommonDialog is invalid.
Line 127: The property name _Version in dlgCommonDialog is invalid.
etc

In the project available  references I have:
Visual Basic For Applications
Visual Basic runtime objects and proceedures
OLE Automation
Microsoft Windows Common Copntrols 5.0
Microsoft FlexGrid Control 5.0
All ticked, and many others which do not seem to me to be applicable.

I may not have told you of all the error messages, but have
endeavoured to give a representation of the applicable ones.

I am wondering if we can somehow enable the Panel property whether
this will finally fix the loading and running problems.

I am becoming more confused fiddling with things that I do not fully
understand, hope this all makes sense.

John

[toc] | [prev] | [next] | [standalone]

#2079

On Sun, 11 May 2014 16:03:38 +0800, John Mott <johnmott@iinet.net.au>
wrote:
>
>
>1) I have V5.0.37.24 installed on win7 64 bit
>
>2) I do not get errors when opening VB5.
>
>3) I do not get errrors opening a simple VB project but do get errors
>trying to open a more complex project.
>
>>
>>Try this:
>>Close the VBIDE.
>>Open the  .vbp file of a troubled project in a text editor and delete
>>the lines that reference comctl32.ocx and comdlg32.ocx. (Or any .oca
>>reference that may have slipped in.)
>>Save the file.
>>Then open the project in VB, open project references, and add the
>>common control components back. (Again, make sure you do not
>>accidently select an '.oca'.)
>>Save the changes to the vbp file and close.
>>Re-open the project and test.
>>
>>Let us know the exact error/s you get, if any.
>>
>>-ralph
>
>I used a text editor to delete lines refering to comctl32.ocx,
>comdlg32.ocx and msflxgrd.ocx and the project then opened in VB but
>showed error messages Error Loading refer to The numerous Frm.logs.
>Log entries refer to invalid properties.
>When I tied to run it I got I got compile error: 
>user defined type not defined
>Dim pn11 as Panel.
>

Perhaps my fault, should have been more clear about how to reconfigure
a project by editing the .VBP file directly:
After deleting the references:
1) open the project with the VBIDE
2) ignore any complaints, errors, warnings, etc.
3) avoid "touching" any vb modules that may be automatically opened in
the editor
4) go immediately to Project References and make your changes.
5) then close the project/VBIDE to save the change
    (If it asks you to save anything other than the project - 
      Select 'NO')
6) then reopen the VBIDE

To insure a competely 'blank' project - no files opened in the VBIDE -
thus no "load errors", you can edit or delete the .VBW (project
workspace) file. It will be recreated when you open the project.

If you did not do this, ie, continue to fiddle in the Project, then
I'm not sure what may or may not have happened as a consequence.
If you still have the original project files, you might replace your
current files and start-over.

For example of why this may be an issue:
Say you have a project that has one Form with a "missing" control. We
will call it MyControl. When the Form is loaded, so to at least
maintain all the code/events behind, VB will replace MyControl with a
PictureBox. At this point it is just a "placeholder". Go to Project
References add the missing control. Then immediately close the
project. When it is reopened MyControl will have been found. However,
if you in any way cause the Form with the PictureBox placeholder to be
*saved* - then the change is permanent.

The latter is an undesirable outcome as the repair is to manually go
back into each module with a text editor and replace all instances of
'PictureBox' with MyControl. For a large project you can use the load
error file to discover those modules that need to be edited. Narrows
the work down a bit, but still a PITA.

However, I'm not sure at this point if any of this is your problem.
Just wanted to let you know for future reference.

>I then attempted to add the common control properties back in.
>They showed as being referenced in the text file.
>Succeeded with the three above mentioned ocx's, but I cannot fathom
>how to add the Panel property back in.
>
>When I try to run the project I get error message saying
>cant add Panels - method or data member not found.
>

As for the Panel control it would help if someone who is currently
using VB5 or has a better memory would enter this discussion.

The Panel was replaced by Frames with VB6, so not availble. I remember
various howls and complaints when porting to VB6, but wouldn't think
it would be an issue if you are still using VB5 Common Controls. Even
if you screwed up existing panels - I think you should be able to at
least add a new one. Unless of course MS actually removed it from the
updated VB5 control???? (Don't panic just mulling it over. <g>)

I will ponder a bit more.

hth
-ralph

[toc] | [prev] | [next] | [standalone]

#2081

<FWIW>
I just discovered the existence of both 5.0/6.0 versions of these 
controls on my Win7 Home Premium netbook after installing MS Office to 
test my VBA mentioned in my recent OP in this NG.

Not sure if this plays into this situation but thought it might shed 
some light on another factor...

-- 
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
  comp.lang.basic.visual.misc
  microsoft.public.vb.general.discussion

[toc] | [prev] | [next] | [standalone]

#2080

On Sun, 11 May 2014 16:03:38 +0800, John Mott <johnmott@iinet.net.au>
wrote:

Additional general comments:


>
>1) I have V5.0.37.24 installed on win7 64 bit
>

This is the correct version for VB5 SP3 Common Controls. This is the
one you need to straighten out your current problem. (I think, but
more later.)

Unfortunately, Microsoft has released several subsequent updated
versions of comctl32.ocx and comdlg32.ocx. All the versions of each
component have the *same* GUID but they are NOT compatible. This
breaks the most hallowed Rule of COM but the very B*stards that should
have known better decided to break it. <g>

At some point something is bound to install an updated version*. This
is particularly nasty since you will likely never notice, because as
be noted current programs run fine - it will only be when something
new is compiled that an error will show up.

A compiled VB program still works with the version it was compiled
with or later versions. However, programs complied with a newer
version will NOT run if an older one is registered. Thus when a new
VB5 program is compiled it will likely need to use the VB6 version.

This is the most often 'fix' - just use the new VB6 MSCOMCTL.OCX
controls. This component does have a new GUID and is self-contained -
does not depend on the comctl32.dll. Which is another component were
often a newer version may be silently installed by another
application.

[Might be worth while to see what version of comctl32.dll you have
installed as well. Perhaps there is a mismatch there as well.]

Confused yet? <bg>

This addresses most of the problems with Common Controls, however as I
noted before not sure where the 'Panel Control' falls in all this.

-ralph

[toc] | [prev] | [next] | [standalone]

#2082

On Sun, 11 May 2014 16:03:38 +0800, John Mott <johnmott@iinet.net.au>
wrote:

More comments:

>
>When I try to run the project I get error message saying
>cant add Panels - method or data member not found.
>

Still trying to run down where and what is a "Panel".


>The various Frm logs are showing messages
>Cannot load control sbar (name of form) ; license not found

This sounds like a pure registration problem. 

However, I am Not sure what an "sbar" is. It may be provided by a
separate component, is not either an intrinsic or common control. You
need to install and register that component.

[Example: TabStrip, ToolBar, and StatusBar are in comctl32, but the
SSTab control is provided by TabCtl32.ocx.]


>and 
>Line 122: Class MSComDlg.CommonDialog of control dlgCommonDialog was
>not a loaded control class.
>Line 125: The property name _ExtentX in dlgCommonDialog is invalid.
>Line 126: The property name _ExtentY in dlgCommonDialog is invalid.
>Line 127: The property name _Version in dlgCommonDialog is invalid.
>etc
>

This is complaining about the comdlg32.ocx. Perhaps with all the
emphasis on comctl32 we forgot to register this one?

It will have the same version number but the TypeLib version will be
different (Ver V1.1 vs. V1.2)

>
>I am wondering if we can somehow enable the Panel property whether
>this will finally fix the loading and running problems.
>
>I am becoming more confused fiddling with things that I do not fully
>understand, hope this all makes sense.
>

Yep.

Don't let it get you down - anyone and everyone that has worked with
VB for very long has run into one or more COM issues while porting,
installing, updating, etc., and had to learn the hard way the nuances
of COM.

Think of it this way - when you finally get it all sorted out you'll
be an expert. It will be all the more easier the next time. <g>

The Rules for COM are quite simple. As long as everyone obeys the
rules all goes well - but if they don't - it gets messy. In this case
it is Microsoft themselves that failed.

-ralph

[toc] | [prev] | [next] | [standalone]

#2083

On Sun, 11 May 2014 14:04:49 -0500, ralph <nt_consulting@yahoo.com>
wrote:

>On Sun, 11 May 2014 16:03:38 +0800, John Mott <johnmott@iinet.net.au>
>wrote:
>
>More comments:
>
>>
>>When I try to run the project I get error message saying
>>cant add Panels - method or data member not found.
>>
>
>Still trying to run down where and what is a "Panel".
>

There used to be a 3-D Panel.
Try installing and/or registering THREED32.OCX.

-ralph

[toc] | [prev] | [next] | [standalone]

#2085

Hi Ralph

Thank you for all your patience.
It is some 10 - 15 years since I did any programming other than for
modification or maintainence and my aging brain is getting forgetful
and stupid.

I have decided to start again from scratch.
I will uninstal VB5 on the Win7 drive and delete all the VB
directories which I tranferred from the XP drive.
Will then re instal VB5 and copy across the VB directories to the Win7
drive.

From the VB help files:

" A Panel object represents an individual panel in the Panels
collection of a StatusBar control.

Remarks

A Panel object can contain text and a bitmap which may be used to
reflect the status of an application.
Use the Panels collection to retrieve, add, or remove an individual
Panel object. 
To change the look of a panel, change the properties of the Panel
object. To modify the properties at design-time, you can change the
properties of the Panel object in the Panels tab of the Properties
Page. At run-time, you can change the Panel object properties in
code."

Strange, but I do not see a Panels tab in the Properties Page.

John




On Sun, 11 May 2014 14:04:49 -0500, ralph <nt_consulting@yahoo.com>
wrote:

>On Sun, 11 May 2014 16:03:38 +0800, John Mott <johnmott@iinet.net.au>
>wrote:
>
>More comments:
>
>>
>>When I try to run the project I get error message saying
>>cant add Panels - method or data member not found.
>>
>
>Still trying to run down where and what is a "Panel".
>
>
>>The various Frm logs are showing messages
>>Cannot load control sbar (name of form) ; license not found
>
>This sounds like a pure registration problem. 
>
>However, I am Not sure what an "sbar" is. It may be provided by a
>separate component, is not either an intrinsic or common control. You
>need to install and register that component.
>
>[Example: TabStrip, ToolBar, and StatusBar are in comctl32, but the
>SSTab control is provided by TabCtl32.ocx.]
>
>
>>and 
>>Line 122: Class MSComDlg.CommonDialog of control dlgCommonDialog was
>>not a loaded control class.
>>Line 125: The property name _ExtentX in dlgCommonDialog is invalid.
>>Line 126: The property name _ExtentY in dlgCommonDialog is invalid.
>>Line 127: The property name _Version in dlgCommonDialog is invalid.
>>etc
>>
>
>This is complaining about the comdlg32.ocx. Perhaps with all the
>emphasis on comctl32 we forgot to register this one?
>
>It will have the same version number but the TypeLib version will be
>different (Ver V1.1 vs. V1.2)
>
>>
>>I am wondering if we can somehow enable the Panel property whether
>>this will finally fix the loading and running problems.
>>
>>I am becoming more confused fiddling with things that I do not fully
>>understand, hope this all makes sense.
>>
>
>Yep.
>
>Don't let it get you down - anyone and everyone that has worked with
>VB for very long has run into one or more COM issues while porting,
>installing, updating, etc., and had to learn the hard way the nuances
>of COM.
>
>Think of it this way - when you finally get it all sorted out you'll
>be an expert. It will be all the more easier the next time. <g>
>
>The Rules for COM are quite simple. As long as everyone obeys the
>rules all goes well - but if they don't - it gets messy. In this case
>it is Microsoft themselves that failed.
>
>-ralph

[toc] | [prev] | [next] | [standalone]

#2090

On Mon, 12 May 2014 16:49:29 +0800, John Mott <johnmott@iinet.net.au>
wrote:

>Hi Ralph
>
>Thank you for all your patience.
>It is some 10 - 15 years since I did any programming other than for
>modification or maintainence and my aging brain is getting forgetful
>and stupid.
>
>I have decided to start again from scratch.
>I will uninstal VB5 on the Win7 drive and delete all the VB
>directories which I tranferred from the XP drive.
>Will then re instal VB5 and copy across the VB directories to the Win7
>drive.
>

If you installed VB5 successfully the first time, I'm not sure a
re-install is going to magically fix your problem, but what the hey.
<g>

Got to thinking of something else that might be going on...
[Be warned as this is bit exotic.]

If you get the error "COMCTL32.OCX could not be loaded". 
Close the project.
Open the .vbp file in a text editor and find the line like ...
      Object = "{long GUID}#1.2#0"; "COMCTL32.OCX"
Copy it and paste to a post.
What I'm interested in is the TypeLib version - the "#1.2#0".

-ralph

[toc] | [prev] | [next] | [standalone]

#2091

Here are the lines of the objects which could not be loaded when I try
to open the project:

Object={6B7E6392-850A-101B-AFC0-4210102A8DA7}#1.3#0; comctl32.ocx
Object={F9043C88-F6F2-101A-A3C9-08002B2F49FB}#1.2#0; COMDLG32.OCX

The file also has:

Object={5E9E78A0-531B-11CF-91F6-C2863C385E30}#1.0#0; msflxgrd.ocx

But I do not think this throws up an error message, but maybe it has
something to do with the StatusBar control which I think is causing
the Panels error.

I have re installed VB5 and copied over the data files, and will not
try your suggestion of deleting the the offending lines and inserting
references.

John

On Mon, 12 May 2014 22:34:35 -0500, ralph <nt_consulting@yahoo.com>
wrote:

>On Mon, 12 May 2014 16:49:29 +0800, John Mott <johnmott@iinet.net.au>
>wrote:
>
>>Hi Ralph
>>
>>Thank you for all your patience.
>>It is some 10 - 15 years since I did any programming other than for
>>modification or maintainence and my aging brain is getting forgetful
>>and stupid.
>>
>>I have decided to start again from scratch.
>>I will uninstal VB5 on the Win7 drive and delete all the VB
>>directories which I tranferred from the XP drive.
>>Will then re instal VB5 and copy across the VB directories to the Win7
>>drive.
>>
>
>If you installed VB5 successfully the first time, I'm not sure a
>re-install is going to magically fix your problem, but what the hey.
><g>
>
>Got to thinking of something else that might be going on...
>[Be warned as this is bit exotic.]
>
>If you get the error "COMCTL32.OCX could not be loaded". 
>Close the project.
>Open the .vbp file in a text editor and find the line like ...
>      Object = "{long GUID}#1.2#0"; "COMCTL32.OCX"
>Copy it and paste to a post.
>What I'm interested in is the TypeLib version - the "#1.2#0".
>
>-ralph

[toc] | [prev] | [next] | [standalone]

#2092

On Tue, 13 May 2014 14:51:52 +0800, John Mott <johnmott@iinet.net.au>
wrote:

>Here are the lines of the objects which could not be loaded when I try
>to open the project:
>
>Object={6B7E6392-850A-101B-AFC0-4210102A8DA7}#1.3#0; comctl32.ocx
>Object={F9043C88-F6F2-101A-A3C9-08002B2F49FB}#1.2#0; COMDLG32.OCX
>
>The file also has:
>
>Object={5E9E78A0-531B-11CF-91F6-C2863C385E30}#1.0#0; msflxgrd.ocx
>
>But I do not think this throws up an error message, but maybe it has
>something to do with the StatusBar control which I think is causing
>the Panels error.
>
>I have re installed VB5 and copied over the data files, and will not
>try your suggestion of deleting the the offending lines and inserting
>references.
>
>John
> 
Error in above, should say WILL try your suggestion, not WILL NOT try.

I have done it again:
Deleted the lines that reference
comctl32.ocx and comdlg32.ocx and made the changes back again with
Project References and closed the file and also deleted the VBW file.

When I try to open it in the VB IDE, I no longer get the error
messages about the two ocx files, but get errors written to all the
log files about Panels and status bar.
Line 39: Class ComctlLib.StatusBar of control sbarAbove was not a
loaded control class.
Line 46: The property name _ExtentX in sbarAbove is invalid.
Line 47: The property name _ExtentY in sbarAbove is invalid.
Line 48: The property name SimpleText in sbarAbove is invalid.
Line 49: The property name _Version in sbarAbove is invalid.
Line 58: The property name Panels in sbarAbove is invalid.
Not the same in all FRM logs but similar.

It seems that lack of a Status Bar control is the problem.

From the VB5 Help Files it seems that Status Bar control is in
comctl32.ocx: See

A StatusBar control provides a window, usually at the bottom of a
parent form, through which an application can display various kinds of
status data. The StatusBar can be divided up into a maximum of sixteen
Panel objects that are contained in a Panels collection.
Syntax

StatusBar

Remarks
A StatusBar control consists of Panel objects, each of which can
contain text and/or a picture. Properties to control the appearance of
individual panels include Width, Alignment (of text and pictures), and
Bevel. Additionally, you can use one of seven values of the Style
property to automatically display common data such as date, time, and
keyboard states.

At design time, you can create panels and customize their appearance
by setting values in the Panel tab of the Properties Page of the
StatusBar control. At run time, the Panel objects can be reconfigured
to reflect different functions, depending on the state of the
application. For detailed information about the properties, events,
and methods of Panel objects, see the Panel Object and Panels
Collection topics.

A StatusBar control typically displays information about an object
being viewed on the form, the object's components, or contextual
information that relates to that object's operation. The StatusBar,
along with other controls such as the Toolbar control, gives you the
tools to create an interface that is economical and yet rich in
information.

Distribution Note   The StatusBar control is part of a group of custom
controls that are found in the COMCTL32.OCX file. To use the StatusBar
control in your application, you must add the COMCTL32.OCX file to the
project. When distributing your application, install the COMCTL32.OCX
file in the user's Microsoft Windows SYSTEM directory. For more
information on how to add a custom control to a project, see the
Programmer's Guide.

I had a look at the properties of the comctl32 .ocx in my version of
Win7 and it shows V 5.00.3714 566 kb 16/1/97.

In my old XP system where the project was created, it shows
V6.00.8105 594 kb 23/5/2000

This suggests to me that theWin7 version is an earlier and smaller
version that the one I have in XP.

What are your thoughts ?

John






>On Mon, 12 May 2014 22:34:35 -0500, ralph <nt_consulting@yahoo.com>
>
>>On Mon, 12 May 2014 16:49:29 +0800, John Mott <johnmott@iinet.net.au>
>>wrote:
>>
>>>Hi Ralph
>>>
>>>Thank you for all your patience.
>>>It is some 10 - 15 years since I did any programming other than for
>>>modification or maintainence and my aging brain is getting forgetful
>>>and stupid.
>>>
>>>I have decided to start again from scratch.
>>>I will uninstal VB5 on the Win7 drive and delete all the VB
>>>directories which I tranferred from the XP drive.
>>>Will then re instal VB5 and copy across the VB directories to the Win7
>>>drive.
>>>
>>
>>If you installed VB5 successfully the first time, I'm not sure a
>>re-install is going to magically fix your problem, but what the hey.
>><g>
>>
>>Got to thinking of something else that might be going on...
>>[Be warned as this is bit exotic.]
>>
>>If you get the error "COMCTL32.OCX could not be loaded". 
>>Close the project.
>>Open the .vbp file in a text editor and find the line like ...
>>      Object = "{long GUID}#1.2#0"; "COMCTL32.OCX"
>>Copy it and paste to a post.
>>What I'm interested in is the TypeLib version - the "#1.2#0".
>>
>>-ralph

[toc] | [prev] | [next] | [standalone]

#2094

On Tue, 13 May 2014 17:12:09 +0800, John Mott <johnmott@iinet.net.au>
wrote:

>On Tue, 13 May 2014 14:51:52 +0800, John Mott <johnmott@iinet.net.au>
>wrote:
>
>>Here are the lines of the objects which could not be loaded when I try
>>to open the project:
>>
>>Object={6B7E6392-850A-101B-AFC0-4210102A8DA7}#1.3#0; comctl32.ocx
>>Object={F9043C88-F6F2-101A-A3C9-08002B2F49FB}#1.2#0; COMDLG32.OCX
>>
>>The file also has:
>>
>>Object={5E9E78A0-531B-11CF-91F6-C2863C385E30}#1.0#0; msflxgrd.ocx
>>
>>But I do not think this throws up an error message, but maybe it has
>>something to do with the StatusBar control which I think is causing
>>the Panels error.
>>
>>I have re installed VB5 and copied over the data files, and will not
>>try your suggestion of deleting the the offending lines and inserting
>>references.
>>
>>John
>> 
>Error in above, should say WILL try your suggestion, not WILL NOT try.
>
>I have done it again:
>Deleted the lines that reference
>comctl32.ocx and comdlg32.ocx and made the changes back again with
>Project References and closed the file and also deleted the VBW file.
>
>When I try to open it in the VB IDE, I no longer get the error
>messages about the two ocx files, but get errors written to all the
>log files about Panels and status bar.
>Line 39: Class ComctlLib.StatusBar of control sbarAbove was not a
>loaded control class.
>Line 46: The property name _ExtentX in sbarAbove is invalid.
>Line 47: The property name _ExtentY in sbarAbove is invalid.
>Line 48: The property name SimpleText in sbarAbove is invalid.
>Line 49: The property name _Version in sbarAbove is invalid.
>Line 58: The property name Panels in sbarAbove is invalid.
>Not the same in all FRM logs but similar.
>
>It seems that lack of a Status Bar control is the problem.
>
>From the VB5 Help Files it seems that Status Bar control is in
>comctl32.ocx: See
>
>A StatusBar control provides a window, usually at the bottom of a
>parent form, through which an application can display various kinds of
>status data. The StatusBar can be divided up into a maximum of sixteen
>Panel objects that are contained in a Panels collection.
>Syntax
>
>StatusBar
>
>Remarks
>A StatusBar control consists of Panel objects, each of which can
>contain text and/or a picture. Properties to control the appearance of
>individual panels include Width, Alignment (of text and pictures), and
>Bevel. Additionally, you can use one of seven values of the Style
>property to automatically display common data such as date, time, and
>keyboard states.
>
>At design time, you can create panels and customize their appearance
>by setting values in the Panel tab of the Properties Page of the
>StatusBar control. At run time, the Panel objects can be reconfigured
>to reflect different functions, depending on the state of the
>application. For detailed information about the properties, events,
>and methods of Panel objects, see the Panel Object and Panels
>Collection topics.
>
>A StatusBar control typically displays information about an object
>being viewed on the form, the object's components, or contextual
>information that relates to that object's operation. The StatusBar,
>along with other controls such as the Toolbar control, gives you the
>tools to create an interface that is economical and yet rich in
>information.
>
>Distribution Note   The StatusBar control is part of a group of custom
>controls that are found in the COMCTL32.OCX file. To use the StatusBar
>control in your application, you must add the COMCTL32.OCX file to the
>project. When distributing your application, install the COMCTL32.OCX
>file in the user's Microsoft Windows SYSTEM directory. For more
>information on how to add a custom control to a project, see the
>Programmer's Guide.
>
>I had a look at the properties of the comctl32 .ocx in my version of
>Win7 and it shows V 5.00.3714 566 kb 16/1/97.
>
>In my old XP system where the project was created, it shows
>V6.00.8105 594 kb 23/5/2000
>

YEP. That's it!

Sorry, I was looking at it "backwards".

Here is a quick answer. I'll come back with more boring details later.

 VB5 came out with Win98. You haven't mentioned the platform you were
on before - but sometime between then and now, your O/S was updated
with VB6 SP5 versions of those controls. You went on working not even
realizing you were no longer using "VB5" controls, but the "VB5
Interfaces - on VB6 Controls".

When you install VB5 you installed the older VB5 versions of comctl32,
BUT not the VB6 comctl32. 

Simple fix, is to go into the project files and change the "#1.3#0" to
"#1.2#0" (ignoring the quotation marks of cours.
    or ... 1.3 to 1.2

That should fix that error.

like I said more details later. ...

-ralph

[toc] | [prev] | [next] | [standalone]

#2095

On Tue, 13 May 2014 08:01:19 -0500, ralph <nt_consulting@yahoo.com>
wrote:


In the following note any of the common control components support
backward-compatibility for previous versions but obviously can't
support anything newer. I now believe that was your actual problem.

My apologies but I made the unfortunate mistake of assuming (what is
the usual case) that you were getting errors because you didn't have
the correct component to support an *older* interface, when the real
problem was you didn't have the correct components to support a
*newer* interface. <g>

[confused yet? <g>]

>>
>>I had a look at the properties of the comctl32 .ocx in my version of
>>Win7 and it shows V 5.00.3714 566 kb 16/1/97.
>>

This is the version that is supplied with the original VB5 edition -
with NO SP's (Service Packs). TypeLib V1.1

This component provides NO support for TypeLib versions greater than
1.1.

If you installed the last VB5 SP - which was SP3 - you would have
version 5.01.4319 of comctl32. TypeLib V1.2

This component provides NO support for TypeLib versions greater than
1.2

When anything Win2k or later installed comctl32 it would have
installed one of these two ...
VB6 (no SP) version 6.00.8022 TypeLib V1.3  <--- Tah Dah!!!
VB6 SP5      version 6.00.8105 TypeLib V1.3

This version provides support for TypeLib's V1.1, V1.2, and V1.3.

[*Note VB5 SP5 was the last version of comctl32. VB6 introduced a new
common controls component MSCOMCTL.OCX. Without going into the details
again - this component did change GUIDS for TypeLibs and removed the
"imcompatibility" problems.]

>>In my old XP system where the project was created, it shows
>>V6.00.8105 594 kb 23/5/2000
>>

This as noted above is the last latest 'n greatest comctr32.

There is probably still an install somewhere, but the easiest solution
is to just copy those components (*see below before you do this) over
to your new box and register them. Remember they have to go into the
syswow64 folder, and you have to make sure you use the regsvr32 FOUND
in the syswow64 folder to register them.

If you do that. Then you can put back the TypeLib version 1.3.

Don't get too mad at me for suggesting this fix earlier. I had you do
a simple change in the project file back to V1.2, simply because this
is the easiest way to test my theory, and because you suggested you
were not that familar with COM nuances - in other words - let's do the
easiest first to make sure we were on the right track. <g>

*All the above was about "comctl32". Stuck to explaining about just
the one to keep it simple. But the same sorry story exists for
comdlg32.ocx as well. AFAIK here are the components that make up the
"common control" suite.

comctl32.ocx
comdlg32.ocx
comct232.ocx  - different file versions but 
comct332.ocx  - these only had one TypeLib version
comctl32.dll
(Might be others you have picked-up over the years - make sure to
preserve your old System32 folder - just in case you need to go back
and grab more.)

Copy all of the newer ones on your older system over to your new box
and register the controls. All your "VB5 projects" should be back to
where they were when you last used it.

Also noticed that your version of comctl32 was the one supplied with
original VB5, but IIRC during earlier posts you seem to demonstrate
that you did have VB5 SP3.

You will probably want to install that SP as well. Microsoft does seem
to supply the SP itself any more - but that only means I can't find
it. <g> 
If you don't have the disk. You can download it from various sites,
for example:
"Visual Studio 97 Service Pack 3 (for Visual Basic)"
http://www.softlookup.com/display.asp?id=8705
(I'm leerly of these 3rd party sites. but if you are careful and scan.
Should be OK.)

The other - more official way - is via the cab files:
http://support.microsoft.com/kb/172991/EN-US

You can also simply copy over any "newer" files on your old box over
to the new one. But note - this can get harry. <lol> Do a good
inventory before you start. Record what you did, and be prepared to
"back-out" at any time. 

Microsoft does supply an "essential" runtime files install for VB5:
"Msvbvm50.exe"
http://support.microsoft.com/kb/180071
But note this is not a SP for the VB5 IDE, it is only the runtime
files to support existing VB5 compiled applications.
But it can save you a lot of trouble if distributing your
applications, you can include it in your package.

Whew! Hope this helps.

-ralph

[toc] | [prev] | [next] | [standalone]

#2096

On Tue, 13 May 2014 09:36:22 -0500, ralph <nt_consulting@yahoo.com>
wrote:

OOPS!

>
>[*Note VB5 SP5 was the last version of comctl32. ...

Should read "VB6 SP5" was the last version of comctl32 ...
(not VB5)

>  ... VB6 introduced a new
>common controls component MSCOMCTL.OCX. 

This should read "VB6 SP6" introduced a new ...

> ... Without going into the details
>again - this component did change GUIDS for TypeLibs and removed the
>"imcompatibility" problems.]

[toc] | [prev] | [next] | [standalone]

#2097

On Tue, 13 May 2014 09:36:22 -0500, ralph <nt_consulting@yahoo.com>
wrote:

OOPS! Again.

>You will probably want to install that SP as well. Microsoft does seem
>to supply the SP itself any more - but that only means I can't find
>it. <g> 

Meant to say "Microsoft DOES NOT seem to supply a download for the VB5
SP3 service pack any more ..."

I only looked at a few of the .cab files I mentioned - some seem SP3
(ie, updated) others I'm not sure about. Sorry. I have not used VB5
since 1998 - so I'm running purely on flumes of a distant memory here.
Sure wish a current VB5 users would reply. <g>

-ralph

[toc] | [prev] | [next] | [standalone]

#2098

On Tue, 13 May 2014 09:36:22 -0500, ralph <nt_consulting@yahoo.com>
wrote:

>The other - more official way - is via the cab files:
>http://support.microsoft.com/kb/172991/EN-US
>
>You can also simply copy over any "newer" files on your old box over
>to the new one. But note - this can get harry. <lol> Do a good
>inventory before you start. Record what you did, and be prepared to
>"back-out" at any time. 

Again. Just to be borishly clear - never attempt to simply XCOPY a
complete VB development platform over to a new box - it has to be
*installed*.

However, AFTER it has been installed, you can attempt to do a manual
"upgrade" by replacing older components with newer ones - just make
sure you register them as you go along. (You may even need to manually
fiddle with the Registry.)

There is where the .cab files become in handy.

[toc] | [prev] | [next] | [standalone]

#2099

On Tue, 13 May 2014 09:36:22 -0500, ralph <nt_consulting@yahoo.com>
wrote:

A couple of thousand words and still mess-up ... lol

Forget copying the components over - You can get all the updates in
one swoop ...

"Microsoft Visual Basic 6.0 Common Controls"
http://www.microsoft.com/en-us/download/details.aspx?id=10019

Never paid attention before, but this updates BOTH the mscomctl.ocx
AND the comctl32.ocx.

Download and install.

-ralph

[toc] | [prev] | [next] | [standalone]

#2104

I did download and install this, and then tried to load the project
but it still came up with ocx error messages,  so I used a text editor
to delete them and used the Project References to make new references.
I am not very familiar with this process so may have bungled.
It then loaded with just one error message written to the log of one
form only saying method or data member not found.

In the window on the left side of the VB IDE it shows the controls
available and only seems to show a limited number which does not
include the Status Bar control and I cannot see how to add it.

After messing about for a while, I got a bit confused so finished up
doing a System Restore and will start again tomorrow.

Maybe I would get a better result by transferring and registering the
old ocx files from the drive which has the old XP files.

John

On Tue, 13 May 2014 13:24:46 -0500, ralph <nt_consulting@yahoo.com>
wrote:

>On Tue, 13 May 2014 09:36:22 -0500, ralph <nt_consulting@yahoo.com>
>wrote:
>
>A couple of thousand words and still mess-up ... lol
>
>Forget copying the components over - You can get all the updates in
>one swoop ...
>
>"Microsoft Visual Basic 6.0 Common Controls"
>http://www.microsoft.com/en-us/download/details.aspx?id=10019
>
>Never paid attention before, but this updates BOTH the mscomctl.ocx
>AND the comctl32.ocx.
>
>Download and install.
>
>-ralph

[toc] | [prev] | [next] | [standalone]

#2106

On Wed, 14 May 2014 17:30:00 +0800, John Mott <johnmott@iinet.net.au>
wrote:

>I did download and install this, and then tried to load the project
>but it still came up with ocx error messages,  so I used a text editor
>to delete them and used the Project References to make new references.
>I am not very familiar with this process so may have bungled.
>It then loaded with just one error message written to the log of one
>form only saying method or data member not found.
>
>In the window on the left side of the VB IDE it shows the controls
>available and only seems to show a limited number which does not
>include the Status Bar control and I cannot see how to add it.
>

The StatusBar is located in the ComCtl32.ocx.

A 'reduced number of available' controls would suggest that the
"install" is not picking up the common controls. You may have to open
Project References -> Components and add them to your VBIDE. But this
seems a tad exotic.

Run the Microsoft mscomctl install package first.

Frankly I get nervous when remote people keep going back and "deleting
down to the water-line (or below)", or "re-starting" thinking this is
in some way is going to resolve anything. Never know for sure how or
what one might be doing or what they are fiddling-with during these
cycles. 

Note: You have to "UN-INSTALL" anything you have installed. For
example, a simple deletion of components or folders often doesn't work
or has unexpected consequences. Experience shows one usually makes it
worse by leaving something behind.

[For example, did you know if you simply move an ActiveX component to
another folder or trash folder - Windows very helpfully, quietly and
silently, re-registers the component in the new folder? ie, it is not
really 'gone'.]

You may have to manually go in and delete the following Registry
entries to insure a clean re-install.
HKEY_CURRENT_USER\Software\Microsoft\VBA\Microsoft Visual Basic 
HKEY_CURRENT_USER\Software\Microsoft\Visual Basic\5.0
(But again we need a VB5 programmer to jump in here.)

good luck

-ralph

[toc] | [prev] | [next] | [standalone]

#2112

Old habits die hard. In the distant past when I was administering a
Unix system, It was a golden rule to do a backup before any software
updates so that we could undo it if it went wrong or stuffed up. This
is why I have a habit of creating a system restore point and restoring
if all did not go well. However, I take note of your comments and will
try to be more brave!

Today I ran the VB6 common control update. This put comctl32.ocx V6.00
8106,  1.28 mb, 15.04.2005 into the sysWOW64 folder.
The comctl32.ocx in the old XP drive system32 folder is V6.00 8105,
594 kb, 23.05.2000. A big difference in size !

In the text editor I deleted the lines for comctl32.ocx + #1.3#0 and
comdlg32.ocx #1.2#0 and then loaded the project into VB5 and used
Project Reference to insert references to Microsoft Windows Common
Controls 5.0 (SP2) and Microsoft Common Dialog Control 5.0 and saved
the project.
When I tried to load the revised project in VB5 It came up with an
error message for one of the frm logs:
class comctlib.status of control sbar(name of form) was not a loaded
control class. I noted that there were only 21 controls showing in the
left hand window of VB5 and they did not include one for StatusBar.
When I tried to run it I got error message:
Method or data member not found frmMain "set pn11 = SbarMain PANELS
(1).
I remarked all the lines on the form refering to Panels and the form
loaded successfully. When I tried to use the menu items to select
other forms, it came up with PANELS error:
Method or data member not found.

I then used the text editor to delete comctl 5.0 (SP2) and used the
project reference to add Microsoft Windows Common Controls 6.0 (SP6)
and saved the project.

Now when I try to load the project into VB5 I am still getting the
error:
Line 64: Class ComctlLib.StatusBar of control sbarDividends was not a
loaded control class.

But there are now 30 controls in the left hand window including
StatusBar. When I try to run it, it still comes up with the PANEL
error, Method or data member not found.
I can view the forms and see the status bar on the bottom of the form
complete with panels.
When I look at the properties of the status bar it does not show a tab
for Panels, but shows a tab for a blank picture.

 I now have these references in the project file:
Object={831FDD16-0C5C-11D2-A9FC-0000F8754DA1}#2.1#0; MSCOMCTL.OCX
Object={F9043C88-F6F2-101A-A3C9-08002B2F49FB}#1.1#0; COMDLG32.OCX
Object={5E9E78A0-531B-11CF-91F6-C2863C385E30}#1.0#0; MSFLXGRD.OCX

I note that inthe project it has COMDLG32.OCX V6.01.9782, 149kb,
9.3.2004 whereas the old XP Drive has 
COMDLG32.OCX V5.00.3714, 16.01.1997, 125kb, 16.1.1997.
I do not think this mismatch could be a problem.
It seems that we are missing the Panels in the StatusBar control.

John



 On Wed, 14 May 2014 07:05:42 -0500, ralph <nt_consulting@yahoo.com>
wrote:

>On Wed, 14 May 2014 17:30:00 +0800, John Mott <johnmott@iinet.net.au>
>wrote:
>
>>I did download and install this, and then tried to load the project
>>but it still came up with ocx error messages,  so I used a text editor
>>to delete them and used the Project References to make new references.
>>I am not very familiar with this process so may have bungled.
>>It then loaded with just one error message written to the log of one
>>form only saying method or data member not found.
>>
>>In the window on the left side of the VB IDE it shows the controls
>>available and only seems to show a limited number which does not
>>include the Status Bar control and I cannot see how to add it.
>>
>
>The StatusBar is located in the ComCtl32.ocx.
>
>A 'reduced number of available' controls would suggest that the
>"install" is not picking up the common controls. You may have to open
>Project References -> Components and add them to your VBIDE. But this
>seems a tad exotic.
>
>Run the Microsoft mscomctl install package first.
>
>Frankly I get nervous when remote people keep going back and "deleting
>down to the water-line (or below)", or "re-starting" thinking this is
>in some way is going to resolve anything. Never know for sure how or
>what one might be doing or what they are fiddling-with during these
>cycles. 
>
>Note: You have to "UN-INSTALL" anything you have installed. For
>example, a simple deletion of components or folders often doesn't work
>or has unexpected consequences. Experience shows one usually makes it
>worse by leaving something behind.
>
>[For example, did you know if you simply move an ActiveX component to
>another folder or trash folder - Windows very helpfully, quietly and
>silently, re-registers the component in the new folder? ie, it is not
>really 'gone'.]
>
>You may have to manually go in and delete the following Registry
>entries to insure a clean re-install.
>HKEY_CURRENT_USER\Software\Microsoft\VBA\Microsoft Visual Basic 
>HKEY_CURRENT_USER\Software\Microsoft\Visual Basic\5.0
>(But again we need a VB5 programmer to jump in here.)
>
>good luck
>
>-ralph

[toc] | [prev] | [next] | [standalone]

#2114

On Thu, 15 May 2014 16:58:27 +0800, John Mott <johnmott@iinet.net.au>
wrote:


>
>In the text editor I deleted the lines for comctl32.ocx + #1.3#0 and
>comdlg32.ocx #1.2#0 and then loaded the project into VB5 and used
>Project Reference to insert references to Microsoft Windows Common
>Controls 5.0 (SP2) and Microsoft Common Dialog Control 5.0 and saved
>the project.
>

Note the version numbers.

>[...]
>I then used the text editor to delete comctl 5.0 (SP2) and used the
>project reference to add Microsoft Windows Common Controls 6.0 (SP6)
>and saved the project.
>[...]
>Now when I try to load the project into VB5 I am still getting the
>error:
>Line 64: Class ComctlLib.StatusBar of control sbarDividends was not a
>loaded control class.
>

This is still squirrelly. 
After you have reloaded your original project . (See below).
Open the .vbp file that is complaining about the "sbar", and send any
directives that refer to that control.

.[...]
>
> I now have these references in the project file:
>Object={831FDD16-0C5C-11D2-A9FC-0000F8754DA1}#2.1#0; MSCOMCTL.OCX
>Object={F9043C88-F6F2-101A-A3C9-08002B2F49FB}#1.1#0; COMDLG32.OCX
>Object={5E9E78A0-531B-11CF-91F6-C2863C385E30}#1.0#0; MSFLXGRD.OCX
>
Note: you are no longer using the same typelib versions. You converted
from using VB6 SP5 components (as was your original) to updated VB6
SP6 components. Not clear if this is a problem or not.

Chewing on too many items at one time. All we were trying to do was 
1) Get the original components on your new box.
    In this case VB6 sp5. 
(The fact you can also install the newer VB6 SP6 components will be
useful later on.)

2) Get your original projects to load without error on the new box.
    Referencing the original components you were using on your old
platform.

3) THEN perhaps make changes to update the projects.

Now that you have the Latest 'n Greatest Common Controls installed on
the box, forget about installed components* and go back and reload
your original projects.

Baby Steps.

-ralph
[*This is assuming this "sbar" is in fact not something else.
Threed.ocx for example.]

[toc] | [prev] | [next] | [standalone]

Page 2 of 3 — ← Prev page 1 [2] 3  Next page →

Back to top | Article view | comp.lang.basic.visual.misc

csiph-web