Creatively Display Parent/Child

[Ken Mayer [dBVIPS]]

Using standard Orders/LineItem tables, I'd like to display the parent &
child in the same (grid-like?) control.
Normally, I'd use 2 grids, an upper grid for the parent, lower grid for
the LineItems.
John Doe OrderNumber OrderDate
LineItem1 details
LineItem2 details
Suzy Chapstick OrderNumber OrderDate
LineItem1 details
LineItem2 details
LineItem3 details
<etc>
A grid would be nice, because I could conditionally highlight the line
item details (yellow if action needed,, etc).... But since the filter
could change to show some or all of the orders, or the Order could
change (by OrderNumber or OrderDate) I'm not sure how the children would
stay with the parent...
The tables won't be huge, but easily in the 5-50k range.... with
normally 1-4 child lineitems per parent record.
I haven't used TreeViews at all, would this be a worthwhile direction?
I'm wondering about performance.... Also thinking if I could use SQL to
generate a temp table to display in a Grid....
The user would need to click on either a LineItem or a parent Order to
open a specific form to respectively update/edit the parent or child
record, the values would then need to be visibly updated.
Any thoughts about this? I don't want to reinvent the wheel if someone
else already has dealt with this issue.
Thanks, Rich Assaf
ps - I thought I had already posted this, but can't find it in Gravity -
sorry if I'm double-posting...)

Rich -- it's here, it's been responded to ...

Ken
--
/(Opinions expressed are purely my own, not those of dataBased
Intelligence, Inc.)/

*Ken Mayer* [dBVIPS]
/Golden Stag Productions/
dBASE at goldenstag dot net
http://www.goldenstag.net/GSP
http://www.goldenstag.net/dbase/dBASEBooks.htm
http://www.goldenstag.net/dbase

[Lysander]

I haven't used TreeViews at all, would this be a worthwhile direction?
I'm wondering about performance.... Also thinking if I could use SQL to
generate a temp table to display in a Grid....

I have been doing this stuff mostly with a treeview to the left and one
or more grids on the right side of a form.

Works like a charm and is very intuitive to the end user.

When building the treeview, just make sure that each treeitem has a
unique ID as a custom property. A treeview could for example host groups
of suppliers on the first level with a group-ID as "ID" for a custom
property. The second level could be made up by suppliers the 3rd by
invoices they charged you with.

On the right side have a grid displaying all (partial) payments to that
specific invoice.


I seem to remember that you did some creative programming in the past,
so - for the future - consider writing a listview-component in .net and
access that from your dBase-application. A "listview" looks similar to
the details window in the windows explorer (with group headers and then
detail records with n fields below).

[Greg Hill]

Rich,

What did you say you are using for a reporting tool?

You said your using VDB and that you aborted Vics printer class right?.
Then I would assume you are using Crystal Reports that was bundled with VDB?

Greg Hill