Should have said that R:Base focus moves to the second table as soon as the
first table's row is entered. The cursor seamlessly moves to the first
field in the second table. Sorry for the confusion.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of ForenSys
Sent: Monday, May 14, 2001 7:43 PM
To: [EMAIL PROTECTED]
Subject: Re: Forms - Adding Multiple Rows to 2nd Table
What do you mean by "activate the second table"?
Regards,
Stephen Markson
ForenSys The Forensic Systems Group
www.ForensicSystemsGroup.com
416 482 2140
----- Original Message -----
From: "Albert" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, May 14, 2001 5:13 PM
Subject: RE: Forms - Adding Multiple Rows to 2nd Table
> Disagree. Using FOR 1 ROW with a second table is a very easy way to, for
> example, add an employee and eligible wage rate codes to a sub-table. The
> FOR 1 ROW causes the form to activate the second table as soon as the
first
> table is complete. Simple. But not for complex data entry - for complex
> data, I would use another procedure.
>
>
> >I would say that virtually no one uses
> >ENTER... FOR 1 ROW with a dependant second table - we've all implemented
it
> >other ways.
