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.

Regards,

Stephen Markson

Reply via email to