Teechart7.ocx as a dll?

[nbp]

Is it posible to replace the TeeChart7.ocx component with a dll version?

We are shipping our product with the ocx component and registering via an InstallShield script. At times we've had some problems registering the component.

Cccasionally it also seems to create a conflict when several version of our software exist on the same machine.

[Pep]

Hi,

Is it posible to replace the TeeChart7.ocx component with a dll version?

We do not have any way to replace it. I think that exists some tools to do this but we don't know a specific one nor have test it.

Cccasionally it also seems to create a conflict when several version of our software exist on the same machine.

It's strange, this should not occur, you should be able to register several TeeChart ActiveX versions ( v6, v7, v8..) to the same machine. In case you ascertain when the problem happens please let us know so we can try to reproduce it here and solve it.

[MarkR]

We're having problems with this as well, and I think it's because we're making some incorrect assumptions about COM registration.

We have two products that are installed separately, and both make use of teechart.ocx v6. Both copy an instance of teechart.ocx into their private installation directory, and both invoke the registration process separately (as a "shared" component instance).

I believe what's happening is that the COM registration entries (in the Windows registry) are simply being over-written by whichever application was installed last. This creates a situation where product un-installation in a specific order can result in un-expected behavior.

So, assuming everything I've said above is correct (please confirm as much), what is the best strategy for sharing teechart.ocx between two completely unrelated applications? Are we pretty much forced to create a "share component" folder and drop an instance in there for registration?

[Marc]

Hello,

The ocx registration is intended as 'one per machine per full version of TeeChart'. So at any one time you could have one TeeChart 5, one TeeChart 6, one teeChart 7 ... etc installed and registered.

If you attempt to re-register a like-version TeeChart ocx version then that shouldn't cause a problem. The registered location will change accordingly and all dependent software should continue to work as intended with the newly registered ocx.

If you wish to avoid problems at de-install time then your installer should do a check for existing installed ocxs before install and save any relevant information to be able to restore it afterwards. For TeeChartAX v6 that would principally be the ocx path at:

Code: Select all

[HKEY_CLASSES_ROOT\CLSID\{536600D3-70FE-4C50-92FB-640F6BFC49AD}\InprocServer32]
@="c:\\yourPath\\TeeChart6.ocx"

An alternative approach could be to check for instances of your other distributed software and to set the registry to activate any ocx at that location when de-installing the currently registered one.

Regards,
Marc Meumann