David Again, this only works with EDIT forms. I brought up a Enter only form in Enter mode. Entered relevant info in the Header section of the form. Then switched (F8) to the second table and entered one line of info. Recorded a Playback with just F2 in it. Then went to the designer, and changed to the second table, added a button to run a eep with the line to playback f2.pla The result is just like a button that has the pre-defined action of Add Row which.... Adds the Header and first row to the appropiate tables and leaves me with a empty form ready to start another record in the first table..
This is not desired. Thanks anyway... was worth the try. This seems to be a flaw/bug/ problem with the way buttons were first intregrated into RBase, and I guess we have to live with it, or at least that's the impression I am given. Razzak has given an example to show how to get around this in the sense of not using buttons in this manner, and as most users would likely do anyway is once a user gets to the end of a row in the second table (tiered in my case) (last column/variable) then pressing ENTER/return key will add this record. I can live with this but it's not optimal.. Later Jim Limburg --- david blocker <[EMAIL PROTECTED]> wrote: > I've read this thread with interest - I agree that you as the developer > should be able to decide in WHICH table you want the "add row" function to > operate and would agree with requesting this enhancement. > > In the meantime, a workaround: > > 1. Keep your "add row" button for the region > 2. The button should run an EEP called ADDROW.EXP or some such name. > 3. The EEP contains these two rows: > PLAYBACK ADDROW.PLY > RETURN > 4. The file ADDROW.PLY is a playback file with the [F2] key recorded in > it. > > I think this should do it > > David Blocker > > ----- Original Message ----- > From: "Alastair Burr" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, March 07, 2002 7:00 PM > Subject: Re: Enter Using > > > > I second that, Ben, edit only in forms as far as possible but particularly > > if there is anything complicated. Saves a few headaches! > > > > Regards, Alastair. > > > > > > ----- Original Message ----- > > From: "Ben Petersen" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Thursday, March 07, 2002 8:00 AM > > Subject: re: Enter Using > > > > > > > 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/ > > ================================================ > 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!? Try FREE Yahoo! Mail - the world's greatest free email! 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/
