Jim The col is a product code with a look up dor the description. It seems that this would add a row with a dup produce code. I think this would confuse some of our users.
I may try the #dup anyway and see what happens. thanks marc At 11:59 AM 03/07/2002 -0900, you wrote: >Marc: >Have you tried adding default value of #Dup to the fields checked in the >rules? >It may solve some problems. > >Just a thought, >Jim Blackburn >Kodiak > >marc wrote: > > > > I too have had problems with the differences between > > Enter Using and Edit Using forms. > > > > Since, we upgraded to 6.5++ we can't use > > several forms in Edit mode to Add rows > > without getting an error message about > > "could not find required matching value" > > > > If we want to look at an invoice for a customer > > and we see we forgot to bill for an item we use > > to press F2 to add a row and type in the item #. > > > > Now, we get those errors unless we uncheck the > > required lookup and set the rules off. > > > > It appears that in 6.1 RBase would not check the > > rules or lookup violations until the row was saved > > but 6.5 checks these things as soon as the row > > is added or inserted. Since, RBase does not > > check these things in ADD mode I thought > > Edit mode would be the same. > > > > marc > > > > At 09:16 AM 03/07/2002 -0700, you wrote: > > >Patrick, > > > > > >I second what Ben says below. > > >Forms working differently between insert and edit has always driven me > nuts. > > > I normally manually insert the row and then use the form in edit mode. > > > > > >Troy Sosamon > > > > > >===== Original Message from [EMAIL PROTECTED] at 3/07/02 1:00 am > > > >Patrick, > > > >fwiw, I only use forms in edit mode w/out a menu or task bar. When > adding > > > >a new record, the preceding routine gets some kind of identifier (inv#, > > > cus#, > > > >key from another table, etc...) and does inserts to create the record to > > > edit. > > > >When a region is involved, there is some logic to maintain a certain > number > > > >of empty lines. This logic is reapplied in subsequent edits. And, (very > > > >important) there is a routine to clean up unused rows under certain > > > >conditions (like the close of the month). > > > >This evolved out of necessity, but I've grown to prefer it. The user > doesn't > > > >need to press a button. I discovered that while you're doing the > > > inserts, I'd > > > >think of other things to go along with it to make the system friendlier, > > > etc. > > > >Ben Petersen > > > > > > > ><<Patrick Murphy wrote: > > > >I have a two-table form, with table two having a region and tiers. > This form > > > >works great using EDIT but when using it to Enter data, I am getting > an odd > > > >result. I have a button set up under table 2 to add a new row in the > tier, > > > >using the pre-defined action. However, when I click that button, it > > > saves the > > > >data into table 1 AND table 2, erases the entered data and gives me a > > > >blank form. I just want to be able to add more than one record in > the tier. > > > >Any help will be appreciated as usual. Pat Murphy [EMAIL PROTECTED] >> > > > > > > > >================================================ > > > >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/ > > > > _________________________________________________________ > > Do You Yahoo!? > > Get your free @yahoo.com address at http://mail.yahoo.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/ _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.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/
