Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

dw.net bug - order of object and library

6 posts in DataWindow .NET Last posting was on 2004-08-10 00:13:37.0Z
Gary B Posted on 2004-08-05 20:59:03.0Z
From: "Gary B" <brisebNO@SPAMbp.com>
Newsgroups: sybase.public.datawindow.net
Organization: 129.230.241.5
X-Newsreader: AspNNTP 1.50 (Takeshi Eto)
Subject: dw.net bug - order of object and library
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: web110.discountasp.net
X-Original-NNTP-Posting-Host: web110.discountasp.net
Message-ID: <41129f97$1@forums-1-dub>
Date: 5 Aug 2004 13:59:03 -0700
X-Trace: forums-1-dub 1091739543 64.79.161.40 (5 Aug 2004 13:59:03 -0700)
X-Original-Trace: 5 Aug 2004 13:59:03 -0700, web110.discountasp.net
Lines: 35
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.datawindow.net:49
Article PK: 124484

Has anyone else run into the problem where the order in which the properties for
the dw object and the library are set in the wrong order, so the datawindow
object fails to load?

The painter generates the InitializeComponent code for the control setting the
relevant properties like this:

this.dataWindowControl1.DataWindowObject = "d_test";
this.dataWindowControl1.LibraryList = "C:\\test.pbl";

But what happens is the first line of code fails, presumably because the library
list has not been set yet, and the control does not display the datawindowobject
even after the second line has run.

The fix is to change the order of the calls, like this:

this.dataWindowControl1.LibraryList = "C:\\test.pbl";
this.dataWindowControl1.DataWindowObject = "d_test";

BUT of course you are doing this in the InitializeComponent method, which the
.NET environment regularly rearranges - it has reverted the code back to the bad
version a couple times on me.

I am thinking I may just declare my own method which sets these properties in
the correct order in the constructor after the call to InitializeComponent.

This is provided FYI, but also to solicit any other suggestions for a
workaround.

Very entusiastic about this product - cant wait to start putting this thing to
work and scrapping a lot of old single-purpose components!

-Gary B
---== Posted via the PFCGuide Web Newsreader ==---
http://www.pfcguide.com/_newsgroups/group_list.asp


Jim O'Neil [Sybase] Posted on 2004-08-06 00:36:01.0Z
From: "Jim O'Neil [Sybase]" <joneil_AT_sybase_DOT_com>
Newsgroups: sybase.public.datawindow.net
Subject: Re: dw.net bug - order of object and library
Message-ID: <htj5h0l51ne6svogcok04v7jev19i7lodu@4ax.com>
References: <41129f97$1@forums-1-dub>
X-Newsreader: Forte Agent 2.0/32.652
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vpn-concord-058.sybase.com
X-Original-NNTP-Posting-Host: vpn-concord-058.sybase.com
Date: 5 Aug 2004 17:36:01 -0700
X-Trace: forums-1-dub 1091752561 158.159.8.58 (5 Aug 2004 17:36:01 -0700)
X-Original-Trace: 5 Aug 2004 17:36:01 -0700, vpn-concord-058.sybase.com
Lines: 48
X-Authenticated-User: teamsybase
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.datawindow.net:53
Article PK: 124496

Well, the requirement to set the library list BEFORE the
DataWindowObject is just that, a requirement. I'm curious though
about the contention that the order of code in the InitializeComponent
method is being rearranged by the .NET environment. I'm not an
experienced .NET developer, but you make that statement like it's a
given. That seems rather random though to me, but I would not
discount that somehow the DW.NET code is regenerating in the wrong
order.

If you have a scenario where this becomes reproducible, please let me
know, but in the interim, I'd say your workaround is a good approach.

On 5 Aug 2004 13:59:03 -0700, "Gary B" <brisebNO@SPAMbp.com> wrote:

>Has anyone else run into the problem where the order in which the properties for
>the dw object and the library are set in the wrong order, so the datawindow
>object fails to load?
>
>The painter generates the InitializeComponent code for the control setting the
>relevant properties like this:
>
>this.dataWindowControl1.DataWindowObject = "d_test";
>this.dataWindowControl1.LibraryList = "C:\\test.pbl";
>
>But what happens is the first line of code fails, presumably because the library
>list has not been set yet, and the control does not display the datawindowobject
>even after the second line has run.
>
>The fix is to change the order of the calls, like this:
>
>this.dataWindowControl1.LibraryList = "C:\\test.pbl";
>this.dataWindowControl1.DataWindowObject = "d_test";
>
>BUT of course you are doing this in the InitializeComponent method, which the
>NET environment regularly rearranges - it has reverted the code back to the bad
>version a couple times on me.
>
>I am thinking I may just declare my own method which sets these properties in
>the correct order in the constructor after the call to InitializeComponent.
>
>This is provided FYI, but also to solicit any other suggestions for a
>workaround.
>
>Very entusiastic about this product - cant wait to start putting this thing to
>work and scrapping a lot of old single-purpose components!
>
>-Gary B


Gary B Posted on 2004-08-06 22:07:07.0Z
From: "Gary B" <brisebgNO@SPAMbp.com>
Newsgroups: sybase.public.datawindow.net
Organization: 63.84.4.1
References: <41129f97$1@forums-1-dub> <htj5h0l51ne6svogcok04v7jev19i7lodu@4ax.com>
X-Newsreader: AspNNTP 1.50 (Takeshi Eto)
Subject: Re: dw.net bug - order of object and library
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: web110.discountasp.net
X-Original-NNTP-Posting-Host: web110.discountasp.net
Message-ID: <4114010b$1@forums-1-dub>
Date: 6 Aug 2004 15:07:07 -0700
X-Trace: forums-1-dub 1091830027 64.79.161.40 (6 Aug 2004 15:07:07 -0700)
X-Original-Trace: 6 Aug 2004 15:07:07 -0700, web110.discountasp.net
Lines: 82
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.datawindow.net:55
Article PK: 124489

Thanks Jim

The way to set these properties in the VS.NET IDE is to fill out the appropriate
fields on the properties tab for the control. The IDE then generates the code in
the InitializeComponent() method on the form, where all the designer-generated
code to initialize the form is stored. A call to InitializeComponent is placed
in the constructor. The IC method is also commented as follows:

/// Required method for Designer support - do not modify
/// the contents of this method with the code editor.

If you do take a chance and modify it, there is no guarantee that your
modifications won't be overwritten the next time you save the form. (In fact,
you will encounter bugs in the designer where it drops vast quantities of code
and controls without warning, particularly where menus are
involved!)Unfortunately, the designer seems to prefer coding the
datawindowobject ahead of the library list, and may move it back to the wrong
order if you do correct it. YOu can code whatever you need in the constructor
after the IC call if you really have to.

I haven't worked with this any further, because I am waiting to receive a
non-evaluation version.

Thanks again
Gary B


On 5 Aug 2004 17:36:01 -0700,
in sybase.public.datawindow.net

Jim O'Neil [Sybase] <joneil_AT_sybase_DOT_com> wrote:
>Well, the requirement to set the library list BEFORE the
>DataWindowObject is just that, a requirement. I'm curious though
>about the contention that the order of code in the InitializeComponent
>method is being rearranged by the .NET environment. I'm not an
>experienced .NET developer, but you make that statement like it's a
>given. That seems rather random though to me, but I would not
>discount that somehow the DW.NET code is regenerating in the wrong
>order.
>
>If you have a scenario where this becomes reproducible, please let me
>know, but in the interim, I'd say your workaround is a good approach.
>
>On 5 Aug 2004 13:59:03 -0700, "Gary B" <brisebNO@SPAMbp.com> wrote:
>
>>Has anyone else run into the problem where the order in which the properties
for
>>the dw object and the library are set in the wrong order, so the datawindow
>>object fails to load?
>>
>>The painter generates the InitializeComponent code for the control setting the
>>relevant properties like this:
>>
>>this.dataWindowControl1.DataWindowObject = "d_test";
>>this.dataWindowControl1.LibraryList = "C:\\test.pbl";
>>
>>But what happens is the first line of code fails, presumably because the
library
>>list has not been set yet, and the control does not display the
datawindowobject
>>even after the second line has run.
>>
>>The fix is to change the order of the calls, like this:
>>
>>this.dataWindowControl1.LibraryList = "C:\\test.pbl";
>>this.dataWindowControl1.DataWindowObject = "d_test";
>>
>>BUT of course you are doing this in the InitializeComponent method, which the
>>NET environment regularly rearranges - it has reverted the code back to the
bad
>>version a couple times on me.
>>
>>I am thinking I may just declare my own method which sets these properties in
>>the correct order in the constructor after the call to InitializeComponent.
>>
>>This is provided FYI, but also to solicit any other suggestions for a
>>workaround.
>>
>>Very entusiastic about this product - cant wait to start putting this thing to
>>work and scrapping a lot of old single-purpose components!
>>
>>-Gary B
>


dfish Posted on 2004-08-06 23:32:51.0Z
From: dfish@_no_spam_sybase.com (Dave Fish [Team Sybase])
Newsgroups: sybase.public.datawindow.net
Subject: Re: dw.net bug - order of object and library
Organization: Sybase Professional Services
Reply-To: nospam_dfish@sybase.com_nospam
Message-ID: <411411eb.118160816@forums.sybase.com>
References: <41129f97$1@forums-1-dub> <htj5h0l51ne6svogcok04v7jev19i7lodu@4ax.com> <4114010b$1@forums-1-dub>
X-Newsreader: Forte Free Agent 1.21/32.243
NNTP-Posting-Host: vpn-dub-148.sybase.com
X-Original-NNTP-Posting-Host: vpn-dub-148.sybase.com
Date: 6 Aug 2004 16:32:51 -0700
X-Trace: forums-1-dub 1091835171 10.22.120.148 (6 Aug 2004 16:32:51 -0700)
X-Original-Trace: 6 Aug 2004 16:32:51 -0700, vpn-dub-148.sybase.com
Lines: 104
X-Authenticated-User: TeamSybase
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.datawindow.net:56
Article PK: 124490

Hi Gary,

I just looked at the generated code in my application and it is set
the same way you describe it. The datawindow object property comes
before the librarylist property. However my application works fine.

I'm wondering if it is related to something else. Is the
datawindowobject property name correct? How about the librarylist?
Basic questions I know, but I'm not sure why your application doesn't
work when mine does.

By the way, I checked this with Visual Basic .NET. I'll try it with C#
now.

Regards,
Dave Fish
Sybase

On 6 Aug 2004 15:07:07 -0700, "Gary B" <brisebgNO@SPAMbp.com> wrote:

>Thanks Jim
>
>The way to set these properties in the VS.NET IDE is to fill out the appropriate
>fields on the properties tab for the control. The IDE then generates the code in
>the InitializeComponent() method on the form, where all the designer-generated
>code to initialize the form is stored. A call to InitializeComponent is placed
>in the constructor. The IC method is also commented as follows:
>
>/// Required method for Designer support - do not modify
>/// the contents of this method with the code editor.
>
>If you do take a chance and modify it, there is no guarantee that your
>modifications won't be overwritten the next time you save the form. (In fact,
>you will encounter bugs in the designer where it drops vast quantities of code
>and controls without warning, particularly where menus are
>involved!)Unfortunately, the designer seems to prefer coding the
>datawindowobject ahead of the library list, and may move it back to the wrong
>order if you do correct it. YOu can code whatever you need in the constructor
>after the IC call if you really have to.
>
>I haven't worked with this any further, because I am waiting to receive a
>non-evaluation version.
>
>Thanks again
>Gary B
>
>
>On 5 Aug 2004 17:36:01 -0700,
> in sybase.public.datawindow.net
>Jim O'Neil [Sybase] <joneil_AT_sybase_DOT_com> wrote:
>>Well, the requirement to set the library list BEFORE the
>>DataWindowObject is just that, a requirement. I'm curious though
>>about the contention that the order of code in the InitializeComponent
>>method is being rearranged by the .NET environment. I'm not an
>>experienced .NET developer, but you make that statement like it's a
>>given. That seems rather random though to me, but I would not
>>discount that somehow the DW.NET code is regenerating in the wrong
>>order.
>>
>>If you have a scenario where this becomes reproducible, please let me
>>know, but in the interim, I'd say your workaround is a good approach.
>>
>>On 5 Aug 2004 13:59:03 -0700, "Gary B" <brisebNO@SPAMbp.com> wrote:
>>
>>>Has anyone else run into the problem where the order in which the properties
>for
>>>the dw object and the library are set in the wrong order, so the datawindow
>>>object fails to load?
>>>
>>>The painter generates the InitializeComponent code for the control setting the
>>>relevant properties like this:
>>>
>>>this.dataWindowControl1.DataWindowObject = "d_test";
>>>this.dataWindowControl1.LibraryList = "C:\\test.pbl";
>>>
>>>But what happens is the first line of code fails, presumably because the
>library
>>>list has not been set yet, and the control does not display the
>datawindowobject
>>>even after the second line has run.
>>>
>>>The fix is to change the order of the calls, like this:
>>>
>>>this.dataWindowControl1.LibraryList = "C:\\test.pbl";
>>>this.dataWindowControl1.DataWindowObject = "d_test";
>>>
>>>BUT of course you are doing this in the InitializeComponent method, which the
>>>NET environment regularly rearranges - it has reverted the code back to the
>bad
>>>version a couple times on me.
>>>
>>>I am thinking I may just declare my own method which sets these properties in
>>>the correct order in the constructor after the call to InitializeComponent.
>>>
>>>This is provided FYI, but also to solicit any other suggestions for a
>>>workaround.
>>>
>>>Very entusiastic about this product - cant wait to start putting this thing to
>>>work and scrapping a lot of old single-purpose components!
>>>
>>>-Gary B
>>


Gary B Posted on 2004-08-09 22:24:54.0Z
Sender: 63e.4117f69b.1804289383@sybase.com
From: Gary B
Newsgroups: sybase.public.datawindow.net
Subject: Re: dw.net bug - order of object and library
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4117faec.677.1681692777@sybase.com>
References: <411411eb.118160816@forums.sybase.com>
X-Original-NNTP-Posting-Host: 10.22.241.42
X-Original-Trace: 9 Aug 2004 15:30:04 -0700, 10.22.241.42
Lines: 118
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 9 Aug 2004 15:16:21 -0700, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 9 Aug 2004 15:24:54 -0700
X-Trace: forums-1-dub 1092090294 10.22.108.75 (9 Aug 2004 15:24:54 -0700)
X-Original-Trace: 9 Aug 2004 15:24:54 -0700, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.datawindow.net:63
Article PK: 124501

Thanks Dave, good to know. When I get set up with a
non-evaluation version, I will look into it again, and post
a new thread if I run into the same problem.

-Gary B

> Hi Gary,
>
> I just looked at the generated code in my application and
> it is set the same way you describe it. The datawindow
> object property comes before the librarylist property.
> However my application works fine.
>
> I'm wondering if it is related to something else. Is the
> datawindowobject property name correct? How about the
> librarylist? Basic questions I know, but I'm not sure why
> your application doesn't work when mine does.
>
> By the way, I checked this with Visual Basic .NET. I'll
> try it with C# now.
>
> Regards,
> Dave Fish
> Sybase
>
>
> On 6 Aug 2004 15:07:07 -0700, "Gary B"
> <brisebgNO@SPAMbp.com> wrote:
>
> >Thanks Jim
> >
> >The way to set these properties in the VS.NET IDE is to
> fill out the appropriate >fields on the properties tab for
> the control. The IDE then generates the code in >the
> InitializeComponent() method on the form, where all the
> designer-generated >code to initialize the form is stored.
> A call to InitializeComponent is placed >in the
> constructor. The IC method is also commented as follows: >
> >/// Required method for Designer support - do not modify
> >/// the contents of this method with the code editor.
> >
> >If you do take a chance and modify it, there is no
> guarantee that your >modifications won't be overwritten
> the next time you save the form. (In fact, >you will
> encounter bugs in the designer where it drops vast
> quantities of code >and controls without warning,
> particularly where menus are >involved!)Unfortunately, the
> designer seems to prefer coding the >datawindowobject
> ahead of the library list, and may move it back to the
> wrong >order if you do correct it. YOu can code whatever
> you need in the constructor >after the IC call if you
> really have to. >
> >I haven't worked with this any further, because I am
> waiting to receive a >non-evaluation version.
> >
> >Thanks again
> >Gary B
> >
> >
> >On 5 Aug 2004 17:36:01 -0700,
> > in sybase.public.datawindow.net
> >Jim O'Neil [Sybase] <joneil_AT_sybase_DOT_com> wrote:
> >>Well, the requirement to set the library list BEFORE the
> >>DataWindowObject is just that, a requirement. I'm
> curious though >>about the contention that the order of
> code in the InitializeComponent >>method is being
> rearranged by the .NET environment. I'm not an
> >>experienced .NET developer, but you make that statement
> like it's a >>given. That seems rather random though to
> me, but I would not >>discount that somehow the DW.NET
> code is regenerating in the wrong >>order.
> >>
> >>If you have a scenario where this becomes reproducible,
> please let me >>know, but in the interim, I'd say your
> workaround is a good approach. >>
> >>On 5 Aug 2004 13:59:03 -0700, "Gary B"
> <brisebNO@SPAMbp.com> wrote: >>
> >>>Has anyone else run into the problem where the order in
> which the properties >for
> >>>the dw object and the library are set in the wrong
> order, so the datawindow >>>object fails to load?
> >>>
> >>>The painter generates the InitializeComponent code for
> the control setting the >>>relevant properties like this:
> >>>
> >>>this.dataWindowControl1.DataWindowObject = "d_test";
> >>>this.dataWindowControl1.LibraryList = "C:\\test.pbl";
> >>>
> >>>But what happens is the first line of code fails,
> presumably because the >library
> >>>list has not been set yet, and the control does not
> display the >datawindowobject
> >>>even after the second line has run.
> >>>
> >>>The fix is to change the order of the calls, like this:
> >>>
> >>>this.dataWindowControl1.LibraryList = "C:\\test.pbl";
> >>>this.dataWindowControl1.DataWindowObject = "d_test";
> >>>
> >>>BUT of course you are doing this in the
> InitializeComponent method, which the >>>NET environment
> regularly rearranges - it has reverted the code back to
> the >bad
> >>>version a couple times on me.
> >>>
> >>>I am thinking I may just declare my own method which
> sets these properties in >>>the correct order in the
> constructor after the call to InitializeComponent. >>>
> >>>This is provided FYI, but also to solicit any other
> suggestions for a >>>workaround.
> >>>
> >>>Very entusiastic about this product - cant wait to
> start putting this thing to >>>work and scrapping a lot of
> old single-purpose components! >>>
> >>>-Gary B
> >>
>


dfish Posted on 2004-08-10 00:13:37.0Z
From: dfish@_no_spam_sybase.com (Dave Fish [Team Sybase])
Newsgroups: sybase.public.datawindow.net
Subject: Re: dw.net bug - order of object and library
Organization: Sybase Professional Services
Reply-To: nospam_dfish@sybase.com_nospam
Message-ID: <411810e2.249446555@forums.sybase.com>
References: <411411eb.118160816@forums.sybase.com> <4117faec.677.1681692777@sybase.com>
X-Newsreader: Forte Free Agent 1.21/32.243
X-Original-NNTP-Posting-Host: vpn-dub-020.sybase.com
X-Original-Trace: 9 Aug 2004 17:18:47 -0700, vpn-dub-020.sybase.com
Lines: 133
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 9 Aug 2004 17:05:03 -0700, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 9 Aug 2004 17:13:37 -0700
X-Trace: forums-1-dub 1092096817 10.22.108.75 (9 Aug 2004 17:13:37 -0700)
X-Original-Trace: 9 Aug 2004 17:13:37 -0700, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.datawindow.net:64
Article PK: 124499

Hi Gary,

The evaluation version should be identical to the production version
with the exception of the time limit.

Can you email me your solution? dfish@n_o_spa_m_sybase.com (remove
the n_o_spa_m_)

Regards,
Dave Fish
Sybase

On 9 Aug 2004 15:24:54 -0700, Gary B wrote:

>Thanks Dave, good to know. When I get set up with a
>non-evaluation version, I will look into it again, and post
>a new thread if I run into the same problem.
>
>-Gary B
>
>
>> Hi Gary,
>>
>> I just looked at the generated code in my application and
>> it is set the same way you describe it. The datawindow
>> object property comes before the librarylist property.
>> However my application works fine.
>>
>> I'm wondering if it is related to something else. Is the
>> datawindowobject property name correct? How about the
>> librarylist? Basic questions I know, but I'm not sure why
>> your application doesn't work when mine does.
>>
>> By the way, I checked this with Visual Basic .NET. I'll
>> try it with C# now.
>>
>> Regards,
>> Dave Fish
>> Sybase
>>
>>
>> On 6 Aug 2004 15:07:07 -0700, "Gary B"
>> <brisebgNO@SPAMbp.com> wrote:
>>
>> >Thanks Jim
>> >
>> >The way to set these properties in the VS.NET IDE is to
>> fill out the appropriate >fields on the properties tab for
>> the control. The IDE then generates the code in >the
>> InitializeComponent() method on the form, where all the
>> designer-generated >code to initialize the form is stored.
>> A call to InitializeComponent is placed >in the
>> constructor. The IC method is also commented as follows: >
>> >/// Required method for Designer support - do not modify
>> >/// the contents of this method with the code editor.
>> >
>> >If you do take a chance and modify it, there is no
>> guarantee that your >modifications won't be overwritten
>> the next time you save the form. (In fact, >you will
>> encounter bugs in the designer where it drops vast
>> quantities of code >and controls without warning,
>> particularly where menus are >involved!)Unfortunately, the
>> designer seems to prefer coding the >datawindowobject
>> ahead of the library list, and may move it back to the
>> wrong >order if you do correct it. YOu can code whatever
>> you need in the constructor >after the IC call if you
>> really have to. >
>> >I haven't worked with this any further, because I am
>> waiting to receive a >non-evaluation version.
>> >
>> >Thanks again
>> >Gary B
>> >
>> >
>> >On 5 Aug 2004 17:36:01 -0700,
>> > in sybase.public.datawindow.net
>> >Jim O'Neil [Sybase] <joneil_AT_sybase_DOT_com> wrote:
>> >>Well, the requirement to set the library list BEFORE the
>> >>DataWindowObject is just that, a requirement. I'm
>> curious though >>about the contention that the order of
>> code in the InitializeComponent >>method is being
>> rearranged by the .NET environment. I'm not an
>> >>experienced .NET developer, but you make that statement
>> like it's a >>given. That seems rather random though to
>> me, but I would not >>discount that somehow the DW.NET
>> code is regenerating in the wrong >>order.
>> >>
>> >>If you have a scenario where this becomes reproducible,
>> please let me >>know, but in the interim, I'd say your
>> workaround is a good approach. >>
>> >>On 5 Aug 2004 13:59:03 -0700, "Gary B"
>> <brisebNO@SPAMbp.com> wrote: >>
>> >>>Has anyone else run into the problem where the order in
>> which the properties >for
>> >>>the dw object and the library are set in the wrong
>> order, so the datawindow >>>object fails to load?
>> >>>
>> >>>The painter generates the InitializeComponent code for
>> the control setting the >>>relevant properties like this:
>> >>>
>> >>>this.dataWindowControl1.DataWindowObject = "d_test";
>> >>>this.dataWindowControl1.LibraryList = "C:\\test.pbl";
>> >>>
>> >>>But what happens is the first line of code fails,
>> presumably because the >library
>> >>>list has not been set yet, and the control does not
>> display the >datawindowobject
>> >>>even after the second line has run.
>> >>>
>> >>>The fix is to change the order of the calls, like this:
>> >>>
>> >>>this.dataWindowControl1.LibraryList = "C:\\test.pbl";
>> >>>this.dataWindowControl1.DataWindowObject = "d_test";
>> >>>
>> >>>BUT of course you are doing this in the
>> InitializeComponent method, which the >>>NET environment
>> regularly rearranges - it has reverted the code back to
>> the >bad
>> >>>version a couple times on me.
>> >>>
>> >>>I am thinking I may just declare my own method which
>> sets these properties in >>>the correct order in the
>> constructor after the call to InitializeComponent. >>>
>> >>>This is provided FYI, but also to solicit any other
>> suggestions for a >>>workaround.
>> >>>
>> >>>Very entusiastic about this product - cant wait to
>> start putting this thing to >>>work and scrapping a lot of
>> old single-purpose components! >>>
>> >>>-Gary B
>> >>
>>