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
_______________________________________________
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/126C50D64EA846C7A9FA19D6334B154E@LaptopW7
** 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.
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.
Mike Copeland wrote on 2011-11-09:
> 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.
>
...
> 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>
>
> 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.
>
...
>
> Thanks,
> Kent
>
Mike,
Since you've subclassed the controls. I believe a complete rebuild of the
project will fix your issue.
If not, there is a way to update the form by using the scx and replacing the
memo fields that are relevant to the record. I found SCATTER and GATHER
worked the best for the couple I've done in the past. This doesn't lose any
settings or code.
Tracy Pearson
PowerChurch Software
_______________________________________________
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/001401cc9f32$eebc49c0$cc34dd40$@powerchurch.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.
Hello Tracy,
I rebuilt the entire project but that did not change the controls on the
forms to the new version.
I opened the form.scx file and found the ctGrid OLE control, but not sure
what field should be changed ?
It looks like the OLE field contains the actual object, and OLE2 contains
the path to the OCX file.
I checked that the OCX in the DBI\Components folder is the new version, but
the form still shows the old version.
I am guessing that I need to change the OLE field ?
Thanks,
Kent
-----Original Message-----
From: profox-bounces@leafe.com [mailto:profox-bounces@leafe.com] On Behalf
Of Tracy Pearson
Sent: Wednesday, November 09, 2011 5:57 PM
To: profox@leafe.com
Subject: RE: DBI control update
Mike Copeland wrote on 2011-11-09:
> 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.
>
...
> 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>
>
> 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.
>
...
>
> Thanks,
> Kent
>
Mike,
Since you've subclassed the controls. I believe a complete rebuild of the
project will fix your issue.
If not, there is a way to update the form by using the scx and replacing the
memo fields that are relevant to the record. I found SCATTER and GATHER
worked the best for the couple I've done in the past. This doesn't lose any
settings or code.
Tracy Pearson
PowerChurch Software
[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/A87301EDE0AF42E3946BF896EAF3567A@LaptopW7
** 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.
Kent Belan wrote on 2011-11-10:
> Hello Tracy,
>
> I rebuilt the entire project but that did not change the controls on the
> forms to the new version.
>
> I opened the form.scx file and found the ctGrid OLE control, but not sure
> what field should be changed ?
>
> It looks like the OLE field contains the actual object, and OLE2 contains
> the path to the OCX file.
>
> I checked that the OCX in the DBI\Components folder is the new version,
but
> the form still shows the old version.
>
> I am guessing that I need to change the OLE field ?
>
> Thanks,
> Kent
>
Kent,
You're guessing right.
Create a form (vfp base form is fine) and add the ole control to it.
If memory serves, this was my method. I only had a couple of places to do
it.
As always, source control and a good back up are recommended. <smile>
Use the newly created form
Find the ole control
SCATTER FIELDS ole, ole2 MEMO NAME ole
Use the existing form
Find the ole control
GATHER NAME ole MEMO
Tracy Pearson
PowerChurch Software
_______________________________________________
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/000501cc9fc4$03a89cd0$0af9d670$@powerchurch.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.
Hello Tracy,
Thanks for the info, I now have all the controls updated to v1.2 and
everything seems to be working fine.
I only had to update 3 controls ctGrid, ctList and ctTree. Had to update
about 30 forms and classes, not bad.
Your directions worked great !!
I like the way these DBI controls look, but they sure are a hassle to work
with ...
-----Original Message-----
From: profox-bounces@leafe.com [mailto:profox-bounces@leafe.com] On Behalf
Of Tracy Pearson
Sent: Thursday, November 10, 2011 11:16 AM
To: profox@leafe.com
Subject: RE: DBI control update
Kent Belan wrote on 2011-11-10:
> Hello Tracy,
>
> I rebuilt the entire project but that did not change the controls on
> the forms to the new version.
>
> I opened the form.scx file and found the ctGrid OLE control, but not
> sure what field should be changed ?
>
> It looks like the OLE field contains the actual object, and OLE2
> contains the path to the OCX file.
>
> I checked that the OCX in the DBI\Components folder is the new
> version,
but
> the form still shows the old version.
>
> I am guessing that I need to change the OLE field ?
>
> Thanks,
> Kent
>
Kent,
You're guessing right.
Create a form (vfp base form is fine) and add the ole control to it.
If memory serves, this was my method. I only had a couple of places to do
it.
As always, source control and a good back up are recommended. <smile>
Use the newly created form
Find the ole control
SCATTER FIELDS ole, ole2 MEMO NAME ole
Use the existing form
Find the ole control
GATHER NAME ole MEMO
Tracy Pearson
PowerChurch Software
[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/6C41E579591440F2941A18A127AC8BE7@LaptopW7
** 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.
On 11/10/2011 3:42 PM, Kent Belan wrote:
> Hello Tracy,
>
> Thanks for the info, I now have all the controls updated to v1.2 and
> everything seems to be working fine.
>
> I only had to update 3 controls ctGrid, ctList and ctTree. Had to update
> about 30 forms and classes, not bad.
>
> Your directions worked great !!
>
> I like the way these DBI controls look, but they sure are a hassle to work
> with ...
I see them in my future...
--
Mike Babcock, MCP
MB Software Solutions, LLC
President, Chief Software Architect
http://mbsoftwaresolutions.com
_______________________________________________
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/4EBC39A7.9070601@mbsoftwaresolutions.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.