Darn, mine isn't behaving that way. But I might have figured out why... The DOS form was actually individual forms (with Screen Restore Off) and when you left one form there was a bunch of eeps to update other tables. I turned it into a 2-tab Windows form, but needed to keep the functionality. Changes to the 1st table can cause updates to the 2nd table, and vice versa. Works great in Edit mode, using PROPERTY TABLE whatever 'REFRESH'.
However, when using "ENTER USING", hitting a 'REFRESH' command causes the "enter using" to reevaluate and basically restarts with a blank form. So note to self: Enter Using and Table Refresh do not work. I cannot test for the form mode to decide whether to perform a Refresh or not because the updates of the other tables still need to happen even if I am in Enter mode. So the easy solution is to do a separate form first to gather data for the first table, then bring up the 2-table form on edit and let them individually add rows for the 2nd table. Karen -----Original Message----- From: MikeB <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Thu, Feb 5, 2015 9:28 pm Subject: [RBASE-L] - Re: Enter Using with 2-table tab form I have a four tab form that I use "Enter Using" that is linked via one column that I do nothing special going from one tab to another. It's been in use for four years at least. I do NOT expose the FK column to the UI on the three other tables, just on the main tab. The behavior is when you tab to the next one, the entries on the first one are of course, saved automatically because the row has been left, so landing on a new row in the lower tables, the FK is automatically entered as it should be. > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Karen > Tellef > Sent: Thursday, February 05, 2015 5:54 PM > To: RBASE-L Mailing List > Subject: [RBASE-L] - Re: Enter Using with 2-table tab form > > I thought the same thing, but there is a "save row" eep already on the > first table, and the row does save (I see it in another open session) > and the save eep evaluates, so the row is there and the BrokNo is valid > at that moment because I created a watch variable to see it and it's > good. But as soon as the cursor lands on the 2nd table, that variable > I have assigned to the BrokNo as a test immediately changes back to a > 0. > > I even went so far as to locate a field for BrokNo on the 2nd table in > the scrolling region. I created a > vKeepBrokNo = .vBrokNo > on exit of the first table and on entry into the 2nd table I do a > property brokno textvalue .vkeepbrokno > > It works at the moment, I see the value in there, but as soon as I try > to save the row, I see the BrokNo field change to a 0 in front of my > eyes and I can't save because of the FK on that field to the PK of the > 1st table. > > > Karen > > > > -----Original Message----- > From: Albert Berry <[email protected]> > To: RBASE-L Mailing List <[email protected]> > Sent: Thu, Feb 5, 2015 4:25 pm > Subject: [RBASE-L] - Re: Enter Using with 2-table tab form > > > I think you might need to refresh table 1 on exit so table 2 can see > it. > Albert > > > On 2/5/2015 3:07 PM, Karen Tellef wrote: > > > Losing my mind here, I must be missing something simple. > > I have a 2-table form, with 2 tabs. When I do an "edit using", > I'm able to go to the 2nd table/tab (which is a many-row) and using the > navigation bar I can add a row and it saves just fine. There is one > common column called BrokNo and it automatically brings it in. > > The issue is that I want to do a "enter using" like the form did > in DOS. However, when they're done with the 1st page and click on the > 2nd page, I can see behind the scenes that the internal BrokNo changes > to a 0 once I click into that second page (using trace and watch > variables). I've tried setting variables all over the place and it > still tries to save that 2nd page with a BrokNo of 0. Is there > something special I need to do? Hard to believe I haven't tried this > before.... Of course, I generally hate using "enter using" but > thought I'd try it for simplicity. > > Karen > > > > > -- > A democracy ..." can only exist until the majority discovers it can > vote itself largess out of the public treasury." > Attributed to Alexander Fraser Tytler 1747-1813
