If your problem turns out to be an overlap of more than one column
with the same name you might consiere creating a view that is
an "editable single table view" and in it's definition use different
names for the overlaping column names.

-- 
Jim Bentley
American Celiac Society
[EMAIL PROTECTED] - email
(973) 325-8837 voice
(973) 669-8808 Fax


---- Troy Sosamon <[EMAIL PROTECTED]> wrote:
> You need check your table structure out.
> R:base multi table forms automatically join on all columns with
> the same 
> name.
> You most likely have multiple columns in your 2 tables w/ the
> same name and 
> different data so that when the form refreshes, the join fails
> to the child 
> table and you loose your data on the screen.  If you go look
> at the data in 
> the second table, it is probably still there.
> 
> One way to fix this is to rename the duplicat column names so
> that only your 
> keys have the same name.
> 
> Troy Sosamon
> 
> ===== Original Message from [EMAIL PROTECTED] at 5/09/02
> 12:32 pm
> >I have what I hope is a simple question with a simple answer!
> >(However it took me a number of lines to explain it!)
> >
> >I have made a form that has (2) tables, the driving table holds
> >header information and the second table has a region for line
> >items.  It is a (2) page form and I have a PUSH button that
> >has a defined function of NEXT TABLE.  This works fine, as
> >when I fill out the first page and then hit the NEXT TABLE
> >button, I go to the second page and can fill in my line items.
> >
> >However, I also placed a PUSH button with the function of
> >PREVIOUS TABLE on the second page.  This button also
> >works fine and allows me to return to the first page and
> >edit/change any data.
> >
> >The problem is that if I push the NEXT TABLE button again
> >to go back to the line items, it returns, but there is no data
> >showing, nor can I enter any additional data.  I want the form
> >to allow going back and forth between the two tables until
> >one feels comfortable that all data is correct and then
> >exit the form.   Is this possible and/or what am I doing
> >that is incorrect with the NEXT & PREVIOUS TABLE
> >functions.
> >
> >Thank you for your assistance!
> >
> >================================================
> >TO SEE MESSAGE POSTING GUIDELINES:
> >Send a plain text email to [EMAIL PROTECTED]
> >In the message body, put just two words: INTRO rbase-l
> >================================================
> >TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
> >In the message body, put just two words: UNSUBSCRIBE rbase-l
> >================================================
> >TO SEARCH ARCHIVES:
> >http://www.mail-archive.com/rbase-l%40sonetmail.com/
> 
> ================================================
> TO SEE MESSAGE POSTING GUIDELINES:
> Send a plain text email to [EMAIL PROTECTED]
> In the message body, put just two words: INTRO rbase-l
> ================================================
> TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
> In the message body, put just two words: UNSUBSCRIBE rbase-l
> ================================================
> TO SEARCH ARCHIVES:
> http://www.mail-archive.com/rbase-l%40sonetmail.com/
>  
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/

Reply via email to