| dataSetRow [message #174995] |
Mon, 03 July 2006 20:21  |
Eclipse User |
|
|
|
Originally posted by: Barrysan.hotmail.com
Ok, I must be the only one missing something really obvious. But, what's
the difference between using row['abc'] and dataSetRow['abc']?
|
|
|
|
| Re: dataSetRow [message #175282 is a reply to message #174995] |
Wed, 05 July 2006 10:35  |
| Eclipse User |
|
|
|
Thanks for asking...I was too embarrassed to ask. I just experimented
until it worked right and followed a pattern, but hadn't figured it out
exactly.
Generally, I bind to the dataset in the outermost container (I put tables
in tables often). If you drag data fields from the data set, then it puts
in the right thing (which is almost always row in my reports). I've not
determined if it is a bug or a feature, but I find the most accurate thing
to do is to drag from the dataset, even if you aren't using the data
field. For example, if you are grouping on a field not in the the
displayed table, don't go and select the group field from the data set
listing on the javascript screen. Make sure it is in the table's
container set (displayed when you double click on a data field in a table)
OR the "None" data set choice you get from choosing the binding tab at the
bottom of the screen(from what I've seen, they both have the same thing).
Perhaps you can avoid the drag by just using row, but I've had more luck
dragging the field over first, deleting it, and then choosing it for
grouping from the Container set. It could just be my dyslexic typing that
makes it better to drag, hwover.
Now-if someone could explain if row_outer has a good use...I've always
gotten the wrong result when I use it. May be the structure of my reports.
|
|
|
| Re: dataSetRow [message #175391 is a reply to message #175282] |
Wed, 05 July 2006 15:19 |
| Eclipse User |
|
|
|
Jett,
Row _outer is used to reference a value from the outer container.
If you are nesting tables and the inner table depends on a outer table
column this
is how it would be referenced.
Jason
"Jett " <jhanna@tlie.org> wrote in message
news:141254e3c7806786d66262d4631e10af$1@www.eclipse.org...
> Thanks for asking...I was too embarrassed to ask. I just experimented
> until it worked right and followed a pattern, but hadn't figured it out
> exactly.
> Generally, I bind to the dataset in the outermost container (I put tables
> in tables often). If you drag data fields from the data set, then it puts
> in the right thing (which is almost always row in my reports). I've not
> determined if it is a bug or a feature, but I find the most accurate thing
> to do is to drag from the dataset, even if you aren't using the data
> field. For example, if you are grouping on a field not in the the
> displayed table, don't go and select the group field from the data set
> listing on the javascript screen. Make sure it is in the table's
> container set (displayed when you double click on a data field in a table)
> OR the "None" data set choice you get from choosing the binding tab at the
> bottom of the screen(from what I've seen, they both have the same thing).
> Perhaps you can avoid the drag by just using row, but I've had more luck
> dragging the field over first, deleting it, and then choosing it for
> grouping from the Container set. It could just be my dyslexic typing that
> makes it better to drag, hwover.
>
> Now-if someone could explain if row_outer has a good use...I've always
> gotten the wrong result when I use it. May be the structure of my
> reports.
>
|
|
|
| Re: dataSetRow [message #175773 is a reply to message #175282] |
Thu, 06 July 2006 21:01 |
| Eclipse User |
|
|
|
Originally posted by: Barrysan.hotmail.com
Thanks for the info, that was helpful. And I hadn't even seen the _outer
option, I'm glad you brought it up.
"Jett " <jhanna@tlie.org> wrote in message
news:141254e3c7806786d66262d4631e10af$1@www.eclipse.org...
> Thanks for asking...I was too embarrassed to ask. I just experimented
> until it worked right and followed a pattern, but hadn't figured it out
> exactly.
> Generally, I bind to the dataset in the outermost container (I put tables
> in tables often). If you drag data fields from the data set, then it puts
> in the right thing (which is almost always row in my reports). I've not
> determined if it is a bug or a feature, but I find the most accurate thing
> to do is to drag from the dataset, even if you aren't using the data
> field. For example, if you are grouping on a field not in the the
> displayed table, don't go and select the group field from the data set
> listing on the javascript screen. Make sure it is in the table's
> container set (displayed when you double click on a data field in a table)
> OR the "None" data set choice you get from choosing the binding tab at the
> bottom of the screen(from what I've seen, they both have the same thing).
> Perhaps you can avoid the drag by just using row, but I've had more luck
> dragging the field over first, deleting it, and then choosing it for
> grouping from the Container set. It could just be my dyslexic typing that
> makes it better to drag, hwover.
>
> Now-if someone could explain if row_outer has a good use...I've always
> gotten the wrong result when I use it. May be the structure of my
> reports.
>
|
|
|
Powered by
FUDForum. Page generated in 0.03427 seconds
Home