You're describing another reason why it's a good idea in these cases to load in rows ahead and then EDIT using: see Razzak's sales models in the Running R:Base Your Way series
David David Blocker [EMAIL PROTECTED] 781-784-1919 Fax: 781-784-1860 Cell: 339-206-0261 ----- Original Message ----- From: "Michael Moser" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <[email protected]> Sent: Sunday, May 08, 2005 2:26 PM Subject: [RBG7-L] - 6.5 to 7.x -- 10 steps forward, 1 step back Hi All, I'm probably (once again) missing something obvious but in 6.5 multi table form buttons were active in only one table. This was really annoying for buttons like "Exit" but worked really nice for buttons like "Add Record" or "Move to Region X". As far as I can tell, in 7.x all buttons are active in all tables so buttons like "Add Record" become problematic. I have been unable to figure out any acceptable eep commands or normal command sequence strategies so that the record is added to the correct table regardless of the active table when the button is activated. The only solution I have found is to have a button eep that closes the form, adds a row to the correct table, then opens the form. Rows added with out closing the form a are not displayed. Unfortunately, closing and re-opening the form completely looses focus on the currently selected records for tables 2, 3, etc. which is not acceptable in most situations. Some of you must have run into the same problem --- any other suggestions? I'm almost dreading the answers -- I'm afraid they are going to be obvious ... Classic "approach avoidance" :-) Thanks, Michael Michael Moser EXAQ Micro Services www.exaq.com Phone: 916-966-8313 Fax: 916-244-0582
