I amazes me that I see no suggestion to use a form in a form to do this one
row thing.
You can start a form on the first table with the one row option. Then have
a button on the form to start an eep to call the second form with the one
row option.
But what puzzles me is why you would have two tables that must have a
one-to-one relationship.
Sounds like a poor design. But, then there may have been circumstances
forcing this. But,
on the other hand, this is seldom the case.
-- Dennis McGrath
mailto:[EMAIL PROTECTED]
-- Productivity Tools for R:Base Programmers
http://www.enteract.com/~mcgrath/dennis
-- Full time consultant with:
SQL Resources Group
Steve Hartmann
Oak Park, IL
mailto:[EMAIL PROTECTED]
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Ben Petersen
Sent: Tuesday, May 15, 2001 5:20 AM
To: [EMAIL PROTECTED]
Subject: Re: Partially Resolved - Forms - Adding Multiple Rows to 2nd
Table
Craig,
> I must say, I am still curious as to how, with the
> classic 1-to-many relationship between the Invoice
> and Line Items tables, that no one else ever tried
> building a form this way
fwiw, after struggling with different "look and feel" goals, I finally
settled on inserts prior to an edit to create a new record... I swag
the max number of line items needed, and then choose an
opportune time to eliminate the excess blank lines (like the closing
of an invoice or posting of a check). I generally have a small
routine for checking the number of available blank rows prior to an
edit, which adds more if needed.
This eliminates the possibilities for orphan rows in the child table
and all sorts of issues with adding new rows to the child table
through a form. Prior I had often created a form for editing and
another for adding, had a raft of eeps, etc... in my case this
method has fewer maintenance issues and net, I think the code
base is smaller.
fwiw,
Ben Petersen
On 15 May 2001, at 12:02, Craig Keenan wrote:
> Thanks again to those who responded or at least took the time to read my
> request for help. I was able to resolve this with a combination of Tom
> Grimshaw's suggestion about an eep checking for data existence after a
> certain point and a button that fires an epp skipping to the last field
> inside the NEW region (gets whites whiter - keeps colors brighter!) around
> my 2nd table and then calls a playback file with the [Enter] key.
>
> I must say, I am still curious as to how, with the classic 1-to-many
> relationship between the Invoice and Line Items tables, that no one else
> ever tried building a form this way, or at least tried it the same way as
> me. No matter, pain...slowly...fading......ahhhhhh.
>
> Craig Keenan
>
> ----- Original Message -----
> From: "Albert" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, May 15, 2001 10:57 AM
> Subject: RE: Partially Resolved - Forms - Adding Multiple Rows to 2nd
Table
>
>
> > Have you tried a NEXTTAB button? Seems that should jump to the second
> > table, adding a row if necessary.
> >
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> > Behalf Of Tom Grimshaw
> > Sent: Monday, May 14, 2001 9:30 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Partially Resolved - Forms - Adding Multiple Rows to 2nd
> > Table
> >
> >
> > G'day Craig,
> >
> > If the sixth field being blank means the remainder of the fields
> > will be blank you could put an entry eep on the seventh field to
> > test that condition and skip to the last field if 6 was blank.
> >
> > At 14:59 14/05/01 -0400, you wrote:
> > >Thank you to all that replied. The issue is now partially resolved -
by
> > >placing a region around the second table's fields (without tiers) I am
> able
> > >to successfully add many rows to the second table in a form. This is a
> > >departure from the DOS functionality and I have not been able to find
it
> > >documented anywhere, but it is at least partially functional now.
> > >
> > >The question now becomes, is there any way to add a row to that second
> > table
> > >besides hitting enter past the last field on the form? [F2], playback
> > >files, Pre-defined button, NewRow in eep don't work. I ask because
there
> > >are 30 fields on the page and only the first 5 are mandatory - trying
to
> > >save the user as many unnecessary keystrokes as possible.
> > >
> > >Thanks for any suggestions,
> > >
> > >Craig Keenan
> > >
> > >----- Original Message -----
> > >From: "A. Razzak Memon" <[EMAIL PROTECTED]>
> > >To: <[EMAIL PROTECTED]>
> > >Sent: Saturday, May 12, 2001 9:33 PM
> > >Subject: Re: Forms - Adding Multiple Rows to 2nd Table
> > >
> > >
> > > >
> > > > At 05:20 PM 5/12/2001 -0400, Stephen Markson wrote:
> > > >
> > > > >However, if you press Enter on the last field of the
> > > > >detail row, then you will automatically go to the next
> > > > >detail row as you want it to.
> > > >
> > > > Stephen,
> > > >
> > > > I would also like to add a simple example for Craig Keenan
> > > > to understand this functionality:
> > > >
> > > > Using TGRB2000 (ver 6.5+) or higher for Windows ...
> > > >
> > > > CONNect Concomp
> > > >
> > > > ENTER USING NewProduct FOR 1 ROW
> > > >
> > > > -- Enter Model and then press [Enter]
> > > > -- Enter Product Name and then [Enter]
> > > > -- Enter Product Desc and then [Enter]
> > > > -- Enter List Price and then [Enter]
> > > >
> > > > Now, you'll be in a region to enter Location, OnHand,
> > > > Cost and Reorder Point.
> > > >
> > > > Keep entering those details and there will be NO PROBLEM!
> > > >
> > > > Hope that helps to understand the functionality of "Adding
> > > > Multiple Rows to 2nd Table".
> > > >
> > > > Have Fun!
> > > >
> > > > Very Best Regards,
> > > >
> > > > Razzak.
> > > >
> > > >
> > > > ===================================-============================
> > > > R:BASE Developers's Conference: http://www.rbase.com/conference
> > > > Official R:BASE List Server: mailto:[EMAIL PROTECTED]
> > > > RBTI Events/Training: http://www.rbase2000.com/events
> > > > R:DCC Members: http://www.rbase2000.com/rdcc
> > > > ================================================================
> > > > R:BASE, Oterro & R:Tango are registered trademarks of RBTI.
> > > > ==================================-=============================
> > > >
> >
> > Warmest regards,
> >
> >
> > Tom Grimshaw
> > coy: Just For You Software
> > tel: 61 (0)2 9552 3311
> > fax: 61 (0)2 9566 2164
> > email: [EMAIL PROTECTED]
> > mobile: 0414 675 903
> > street: 3/66 Wentworth Park Rd Glebe NSW 2037
> > post: PO Box 470 Glebe NSW 2037 Australia
> > temp web site: 210.9.46.35
> >
> > _/_/_/_/_/_/_/_/ _/_/_/_/_/_/ _/ _/ _/_/_/_/_/
> > _/ _/ _/ _/ _/
> > _/ _/ _/ _/ _/
> > _/ _/_/_/_/ _/ _/_/_/_/_/
> > _/ _/ _/ _/
> > _/ _/ _/ _/ _/
> > _/ _/ _/ _/_/_/_/_/
>
>
