Matthew, What I meant to say is that if you have a column in the header table called "customer" and a column in the detail table called "customer" as well, the data will not show in the detail.
As the Highlander said, "There can only be one!" And that should be your linking column. Jan -----Original Message----- From: Matthew Brock <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: Wed, 2 Apr 2014 10:22:06 -0700 (PDT) Subject: [RBASE-L] - Re: Scrolling Region There is only one linking key between those tables. In the "Columns" view it shows a FK* next to the key and when i look at the rules The column names do not have the #, i just typed it in to reduce what i had to type in. It is actually Invoice_Number Thanks, Matthew D. Brock IT Specialist American Fireworks 1315 Hwy 71 W Bastrop, Tx 78602 From: jan johansen <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Wednesday, April 2, 2014 11:48 AM Subject: [RBASE-L] - Re: Scrolling Region Matthew, Also look to see that THERE IS ONLY ONE LINKING column between header and footer i.e. invoiceid. The use of # in column names is highly discouraged now. Jan -----Original Message----- From: Matthew Brock <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: Wed, 2 Apr 2014 09:27:20 -0700 (PDT) Subject: [RBASE-L] - Scrolling Region I am converting some forms over and a few of them have a scrolling Region. The data in the region never gets read in when you do an edit. Is there some field that needs to be set for this? The form is being used as a transaction for a customer. so the top of the form is from the invoice_header table. This has information like cust_number, invoice_#, etc.. The scrolling region has data like item number, item description, quantity, total, etc. It is read from table invoice_trans which is associated with invoice_header by the invoice_#. It is like it doesn't know what the invoice_# is to grab the data for in the invoice_trans table. Can someone help? Thanks, Matthew D. Brock
