Welcome to the wonderful world of OCX! (aka "OCX HELL")

Here's my understanding...how I deal with it...your mileage and my

smarts may vary depending on caffeine intake.

When DBI release a new anything, I install it (to register it in the

Windoze registry) and I leave all the older components (previous

versions from DBI) alone. Just put the new gadgets in a new folder.

As for the use of those OCX gadgets in your applications, for all

references of any OCX on any form, you have to modify the form to use

the new OCX version explicitly. This is done by manually removing the

old OCX device, adding the new one, and re-entering all the settings and

code snippets in the new OCX.

I am not aware of any way to just "update" the OCX file with a new one,

because there are a lot of values stored in the registry to identify

those OCX controls that are above and beyond, but explicitly necessary,

to the version number you see and think about (v1.1 and v1.2).

If there's an easier way to go about this, I'd love to hear about

it...I've been wrasslin' DBI OCX controls for over 12 years.

Mike Copeland

-------- Original Message --------

Subject: DBI control update

From: Kent Belan <kbelan@mchsi.com>

To: profoxtech@leafe.com

Date: 11/9/2011 3:14 PM

Hello,

I guess this would apply to any OCX control update.

I just updated my DBI controls from v1.1 to v1.2.

Three of the controls that where updated, I use in my project, ctList,

ctTree and ctGrid.

I have subclassed all the dbi controls into a separate class and use that

class to add objects to forms.

So I updated the DBIControls class and each shows the new version, but when

I go to a form that uses the object, it is still showing the old OLECLASS,

not the new version of the control ?

How do I get all my forms to show they are using the new updated subclass

objects ?

Thanks,

Kent

[excessive quoting removed by server]

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://leafe.com/mailman/listinfo/profox

OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/4EBAF115.6010400@ggisoft.com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.