Your first paragraph is great, I really enjoyed the logic behind it.
Your second paragraph is incorrect, as I found, you have to first place a
region around the 2nd table before this happens. I am unsure at what point
this became mandatory for this functionality to work (as it worked fine in
my DOS version without a region, just being in the 2nd table was
satisfactory), I am still trying to find this in the current documentation
and the printed documentation for 5.5 Win.
As for accepting things the way they are, that is a recipe for disaster.
And the strangest thing - until there was a little controversy, I didn't get
one response to my request for help. And I'm far from being embarrassed,
sorry to disappoint you. In my mind, you responding with a condescending
attitude to what began as polite requests for help should embarrass the hell
out of you, especially seeing as you didn't have the complete correct answer
as you assumed you did.
As for my bet...how much did I lose? Answer: a weeks productivity.
Craig Keenan
----- Original Message -----
From: "ForenSys" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, May 12, 2001 5:20 PM
Subject: Re: Forms - Adding Multiple Rows to 2nd Table
> When you press F2, RBase assumes you want to save the first table row as
> well. This is not unreasonable given that it's quite common for the two
> tables to have a PK-FK relationship. Even if you don't have an FK from the
> second table to the first, do you really want to save the details without
> saving the header? Of course, if you save the header, that's your "1 ROW"
> and the form will close.
>
> 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.
>
> As to your response to "Razzak's Reply", I should tell you that Razzak
> commonly uses capitals for emphasis (he isn't shouting) despite the common
> email etiquette. My experience is that it is best to accept reality the
way
> it is on this list: it saves frustration; it will get you more help; and
it
> will save the embarassment of a diatribe based on a problem that doesn't
> really exist. You have lost the bet you made in your email. How much was
it
> for?
>
> Regards,
>
> Stephen Markson
> ForenSys The Forensic Systems Group
> www.ForensicSystemsGroup.com
> 416 482 2140
>
> ----- Original Message -----
> From: Craig Keenan
> To: [EMAIL PROTECTED]
> Sent: Tuesday, May 08, 2001 11:29 AM
> Subject: Forms - Adding Multiple Rows to 2nd Table
>
>
> I am in the process of attempting to convert to Windows 6.5+ from 4.5+ and
> am having a problem with an order entry form - namely, I am unable to add
> more than one row to the second table (line items) on the form. The form
is
> brought up with the "Enter Using ... For 1 Row". The line items table is
> the second table on the form and as such should not be affected by the
"For
> 1 Row" constraint. When I try to add a 2nd row (tried [F2], from the
menu,
> and with a push button), it saves the 1 row for both tables exists the
form
> completely. I would suspect that it is exiting because adding another row
> is violating "For 1 Row", but since I am defiantly in the 2nd table when
> attempting this (on a separate page, no columns or variables from the
first
> table are on this page, have to hit [shift]+[F8] to get there), I'm not
sure
> what the problem is. I've been scratching my head over this for over 2
days
> now, any suggestions would be greatly appreciated.
>
> Thank you,
>
> Craig Keenan
