PDA

View Full Version : child file too big for a grid



Jim Mulenos
21-Jan-2005, 08:51 AM
parent file: DOC
child file: NOTIFY

1) I have a parent file DOC built on a unique doc.number

2) I have a child file NOTIFY which relates to parent file DOC and holds
the name, address, phone numbers and comments for each party to be notified
in this DOC. There might be no parties to notify in a particular doc, there
might be as many as ten.


THE CHALLENGE:

Now the dbview in my (altered) mind, looks something like an invoice-style
header / detail layout. However, there are too many fields that are too
big, to use a dbgrid for the child section of this view.

Does anyone have any ideas on how to _nicely_ solve this? Many thanks in
advance.


Jim

Erik Zimmerman
21-Jan-2005, 09:58 AM
Jim,

Place the dbGrid in a dbContainer which has its server set to the same as
the dbGrid. Let the dbGrid display the most important fields and place the
overflow fields in dbForms within the dbContainer. I think Peter Donovan
did some work in this area to ensure that the child_table_state behavior is
respected by the dbForms by modifying the dbContainer to force saving upon
exiting. I would check the "Open Source" group more. I think you will find
something there that will help.

Erik



"Jim Mulenos" <Jim@AssetResearch.com> wrote in message
news:obFm0%237$EHA.5748@dacmail.dataaccess.com...
> parent file: DOC
> child file: NOTIFY
>
> 1) I have a parent file DOC built on a unique doc.number
>
> 2) I have a child file NOTIFY which relates to parent file DOC and holds
> the name, address, phone numbers and comments for each party to be
notified
> in this DOC. There might be no parties to notify in a particular doc,
there
> might be as many as ten.
>
>
> THE CHALLENGE:
>
> Now the dbview in my (altered) mind, looks something like an invoice-style
> header / detail layout. However, there are too many fields that are too
> big, to use a dbgrid for the child section of this view.
>
> Does anyone have any ideas on how to _nicely_ solve this? Many thanks in
> advance.
>
>
> Jim
>
>

Tod Brannen
21-Jan-2005, 09:59 AM
Jim,
I do this all the time. Just place a small grid on the left with the
identifying field of the Notify, maybe the last name of the person . Then on
the right side put all the other fields. As you scroll down the grid, the
data on the right side will change for each name. See the Contacts sample.
You have to change the grid not to wrap. And you have to add code for when
you click off of the child grid. But it is all there in the Contacts sample.

HTH

Tod Brannen

"Jim Mulenos" <Jim@AssetResearch.com> wrote in message
news:obFm0%237$EHA.5748@dacmail.dataaccess.com...
> parent file: DOC
> child file: NOTIFY
>
> 1) I have a parent file DOC built on a unique doc.number
>
> 2) I have a child file NOTIFY which relates to parent file DOC and holds
> the name, address, phone numbers and comments for each party to be
notified
> in this DOC. There might be no parties to notify in a particular doc,
there
> might be as many as ten.
>
>
> THE CHALLENGE:
>
> Now the dbview in my (altered) mind, looks something like an invoice-style
> header / detail layout. However, there are too many fields that are too
> big, to use a dbgrid for the child section of this view.
>
> Does anyone have any ideas on how to _nicely_ solve this? Many thanks in
> advance.
>
>
> Jim
>
>

JimNC9
21-Jan-2005, 10:33 AM
In the details section use a dbgrid with just the name and then use a zoom
view to see the rest of the details. There aren't many choices unless
someone has a multiline dbgrid, meaning, one record displays on two or more
lines.

Jim /*

WebApp Hosting
http://www.advanceddesignsinc.com/Web%20Hosting.htm



"Jim Mulenos" <Jim@AssetResearch.com> wrote in message
news:obFm0%237$EHA.5748@dacmail.dataaccess.com...
> parent file: DOC
> child file: NOTIFY
>
> 1) I have a parent file DOC built on a unique doc.number
>
> 2) I have a child file NOTIFY which relates to parent file DOC and holds
> the name, address, phone numbers and comments for each party to be
> notified
> in this DOC. There might be no parties to notify in a particular doc,
> there
> might be as many as ten.
>
>
> THE CHALLENGE:
>
> Now the dbview in my (altered) mind, looks something like an invoice-style
> header / detail layout. However, there are too many fields that are too
> big, to use a dbgrid for the child section of this view.
>
> Does anyone have any ideas on how to _nicely_ solve this? Many thanks in
> advance.
>
>
> Jim
>
>

Mark Powers
21-Jan-2005, 10:59 AM
Jim:
I've solved it with the old "zoom" features. Put the fields you choose
in the grid but have a double click to popup a dialog for the other
fields. Of course the zoom keys should be setup to do this also -
<Alt><F9>.
Mark

Jim Mulenos wrote:
> parent file: DOC
> child file: NOTIFY
>
> 1) I have a parent file DOC built on a unique doc.number
>
> 2) I have a child file NOTIFY which relates to parent file DOC and holds
> the name, address, phone numbers and comments for each party to be notified
> in this DOC. There might be no parties to notify in a particular doc, there
> might be as many as ten.
>
>
> THE CHALLENGE:
>
> Now the dbview in my (altered) mind, looks something like an invoice-style
> header / detail layout. However, there are too many fields that are too
> big, to use a dbgrid for the child section of this view.
>
> Does anyone have any ideas on how to _nicely_ solve this? Many thanks in
> advance.
>
>
> Jim
>
>

Jim Mulenos
21-Jan-2005, 12:34 PM
Erik, Todd, Jim and Mark...

Masterful ideas.

Thank you so very much

Jim