Why not. Otherwise your choice is to update the dataset AFTER a save to disk. I can't say definitively that either approach is less time consuming to construct, so....
> -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Mike > Sent: Sunday, October 06, 2013 12:24 PM > To: RBASE-L Mailing List > Subject: [RBASE-L] - RE: Updating hidden fields on a form (Version 9.5 > 32) > > Combine property commands with hidden fields? > > Sent from my iPhone > > On Oct 6, 2013, at 12:00 PM, "MikeB" <[email protected]> wrote: > > > That would work on an EDIT, but on ENTER, a new primary key would > > still be in the edit buffer of the form and not saved to disk yet. > > > > You would have to save and continue to do an update on the referenced > > row assuming it has a primary key to reference its uniqueness (or > > insert = last?). > > > > > > I would use Property commands if it were me since you are dealing > with > > the current instance of the dataset. > > > > > > > >> -----Original Message----- > >> From: [email protected] [mailto:[email protected]] On Behalf Of Tony > >> IJntema > >> Sent: Sunday, October 06, 2013 11:15 AM > >> To: RBASE-L Mailing List > >> Subject: [RBASE-L] - RE: Updating hidden fields on a form (Version > >> 9.5 > >> 32) > >> > >> Mike, > >> > >> > >> > >> The way you could solve this problem is: > >> > >> 1. Store the primary key of the current row in a variable, which > is > >> defined in the variable forms > >> > >> 2. Place a button (for instance a speed button on the form > >> > >> 3. Put a procedure in this button when pressed, like > >> > >> perform your calculations for the various columns > >> > >> Update <tablename> set ...... where PK_column = .V_PK_Column > >> > >> > >> > >> > >> > >> There is no need for defining the fields on the form > >> > >> Tony > >> > >> > >> > >> From: [email protected] [mailto:[email protected]] On Behalf Of > >> Michael J. Sinclair > >> Sent: zondag 6 oktober 2013 16:23 > >> To: RBASE-L Mailing List > >> Subject: [RBASE-L] - Updating hidden fields on a form (Version 9.5 > >> 32) > >> > >> > >> > >> Hi all, > >> > >> > >> > >> I have a form with multiple tiers that is updating columns in a > table. > >> I want the user to enter the data into some of the fields that are > >> visible on the form. I would like the form to update the rest of the > >> columns without the user being involved at all. I don't even want > the > >> user to see the other fields/columns that are being updated. > >> > >> > >> > >> Long ago before we had EEPS, I created form variables to do the job > >> of updating columns that were not on the form. It worked fine, but > >> now, if I have lots of data, that seems to slow the form down. > >> > >> > >> > >> What is the best way to have my form update the hidden columns > >> without having a visible field on the form for only the current row? > >> > >> > >> > >> I can make the field have a height and width of 0 and 0 and remove > it > >> from the tab sequence and use the property command to do the update. > >> > >> > >> > >> I think there is a property that I can use in the before start EEP > to > >> hide the fields I want hidden and use the property command to do the > >> update. > >> > >> > >> > >> I can create form variables and live with the speed. > >> > >> > >> > >> I can create an app that runs through the data after the form is > >> closed to update the fields. > >> > >> > >> > >> What is the best way to update just the current row/tier as the user > >> enters data? > >> > >> > >> > >> Mike > > > >
