I'll be there, with my checkbook...and my brain! -----Original Message----- From: A. Razzak Memon [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 25, 2004 9:20 AM To: RBG7-L Mailing List Subject: [RBG7-L] - Re: Enter for n rows
Dawn, You know Sami Aaron is keeping track of all DUHs (small or big) and will be more than happy to collect fines at the Fall 2004 R:BASE Developers' Conference. Make sure to bring your checkbook <g>. Very Best R:egards, Razzak. At 08:34 AM 8/25/2004 -0400, Dawn Oakes wrote: >Now that's a big duh... I do that very thing in another app! >See, I said I wasn't thinking straight yesterday. I slept in late this >morning...hopefully my brain will appreciate it and work more >effectively today! > > >-----Original Message----- >From: A. Razzak Memon [mailto:[EMAIL PROTECTED] >Sent: Tuesday, August 24, 2004 9:12 PM >To: RBG7-L Mailing List >Subject: [RBG7-L] - Re: Enter for n rows > >At 05:46 PM 8/24/2004 -0400, Dawn Oakes wrote: > > >I figured as much....odd that I didn't notice in 6.5. > >The thing is, most of the time, the user can enter as many rows as > >they > > >want. But in certain circumstances (certain conditions in the master > >table), I would want to restrict to one row. > > >Dawn, > >In that case, why not INSERT one blank row in MasterTable (with PRIMARY >Key, etc.) and one matching row in SlaveTable (with FOREIGN Key, etc.) >and then simply use the following >command: > >Example: > >INSERT INTO MasterTable (PrimaryKeyColumn) VALUES (1234) INSERT INTO >SlaveTable (ForeignKeyColumn) VALUES (1234) > >EDIT USING MasterTableForm WHERE COUNT = INSERT > >The form will only have one matching row in SlaveTable. > >You can disable or hide other unnecessary buttons using the PROPERTY >command as "On After Start EEP". > >Now you have exactly what you want! > >Hope that helps! > >Very Best R:egards, > >Razzak.
