Installation of TeeChart Pro ActiveX 5.0

[Mike Kaufmann]

Hi
I use TeeChart Pro Active X v.5.0.3.1. My setup installs and registers the ocx file in the folder "C:\WINDOWS\system32".

The problem occurs, if an other program installs the version v.5.0.4.0 in the directory "C:\WINDOWS\system32". Then the line "TChart1.Legend.ColumnWidthAuto = False" in my VB6 Program fails on the target system. I think the interface has changed in version v.5.0.4.0.

Is there any way to run TeeChart Pro Active X v.5.0.3.1 and v.5.0.4.0 on the same system and use the different interfaces?

With Best Regards
Mike

[Narcís]

Hi Mike,

I'm afraid not. Only one *.ocx file of each TeeChart version can be registered in a machine at the same time. On the other hand, different TeeChart versions (v5, v6, v7, v8, ...) can coexist in the same machine.

[Mike Kaufmann]

There is no solution to run the two programs on the same system, if my program is using v.5.0.3.1 and the other program is using v.5.0.4.0?

What I don't understand:
I am able to set some propoerties of the TeeChart-Control even if the ocx with Version v.5.0.4.0 is registered and my program uses v.5.0.3.1. The program crashes not till a value is assigned to the property Legend.ColumnWidthAuto.

If this property is no more supported in v.5.0.4.0, then a new class id (CLSID) should be assigned to v.5.0.4.0. Why uses the version v.5.0.3.1 the same CLSID as the version v.5.0.3.1 even if the interface has changed?

Kind Regards
Mike

[Narcís]

Hi Mike,

I am able to set some propoerties of the TeeChart-Control even if the ocx with Version v.5.0.4.0 is registered and my program uses v.5.0.3.1. The program crashes not till a value is assigned to the property Legend.ColumnWidthAuto.

Even if you build your applications with v5.0.3.1, if you run it on a machine with v5.0.4.0 it will use v5.0.4.0. It uses the version registered on the machine.

If this property is no more supported in v.5.0.4.0, then a new class id (CLSID) should be assigned to v.5.0.4.0. Why uses the version v.5.0.3.1 the same CLSID as the version v.5.0.3.1 even if the interface has changed?

This behaviour may not have changed intentionally, this could be a bug. v5.0.6.0 and v5.0.7.0 versions are also available at the client area. You could try if any of this versions solve the problem for you.

[Mike Kaufmann]

Hi Narcís

Even if you build your applications with v5.0.3.1, if you run it on a machine with v5.0.4.0 it will use v5.0.4.0. It uses the version registered on the machine.

Right:

This behaviour may not have changed intentionally, this could be a bug. v5.0.6.0 and v5.0.7.0 versions are also available at the client area. You could try if any of this versions solve the problem for you.

Question:
Do you know if version v.5.0.6.0 and v.5.0.7.0 respectively use the same CLSID as v.5.0.4.0? Otherwise the other software will fail…
Do you know what property I've to use, if the property Legend.ColumnWidthAuto is not longer supported?

[Narcís]

Hi Mike,

Do you know if version v.5.0.6.0 and v.5.0.7.0 respectively use the same CLSID as v.5.0.4.0? Otherwise the other software will fail…

Yes, but I don't think why I should fail. Any project using v5 will just use the v5 .ocx registered on the machine where it is being executed.

Do you know what property I've to use, if the property Legend.ColumnWidthAuto is not longer supported?

I don't think so. Could you please let us know which is the exact problem you have with it so that we can check if this is a TeeChart problem?

Thanks in advance.

[Mike Kaufmann]

Hi Narcís

I don't think so. Could you please let us know which is the exact problem you have with it so that we can check if this is a TeeChart problem?

The problem is:
If I assign a value in my VB6 program to the property Legend.ColumnWidthAuto, when the ocx v.5.0.4.0 on the target system is registred, then the error message "The method `~` for the object `~`failed".

My VB-Code:
With TChart1
.AutoRepaint = False
.Panel.Color = &H8000000F
.Legend.ColumnWidthAuto = False
...
End With

[Narcís]

Hi Mike,

This works fine for me here using v5.0.6.0. Could you please check if this version solves the problem for you?

Thanks in advance.