I didn't mean that it had to have focus on the specific componentID to get its ComponentID, I meant a component of the selected row had to have focus.
> -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of > [email protected] > Sent: Friday, November 14, 2014 9:55 AM > To: RBASE-L Mailing List > Subject: [RBASE-L] - RE: On Row Entry EEP > > Thank you for the responses. > > It is good to know more how the GetProperty command works. I would not > have guessed that you had to have focus on the component ID for it to > work. It is correct that the DB Edit control in question was 6th in > order so when the next row was selected, most often, one would not have > it focused (but could have). Do I understand you correctly that if I > have 20 data fields on a form, each with thier own unique component ID > and I have a Getproperty command using the component ID of the 10th > data field in the ON ROW ENTRY, when I move the next row the > GetProperty command retrieves the value of whatever component is > focused, regardless of the ID list in the command? OR that the > Getproperty command does not obtain any value unless focus is on the ID > listed? Either way, this is a new understanding for me. > > I used the example of F8 and F7 as it was the easiest and most clear > example of making the scenario happen for others to replicate. > Actually I do not use F7 or F8 so there is no need to abandon it. I > have Bit Buttons defined with EEP's using NEXT, PREV,FIRST AND LAST on > this form. The navigator if fine, but on this particular form, the > placement, look and need to to have other code made custom buttons the > best bet. > > This is not an issue for me at this time. Instead of using the > GetProperty, i simply defined a variable = DBEdit field. as in the "old > days". It works perfectly and there is no timing issue in that I can > be in any field when moving from one row to the other. No duplicate > code on every fields eep either. > > Thanks again, > Bob > > ________________________________ > > From: "Byerley, Mike" <[email protected]> > To: "RBASE-L Mailing List" <[email protected]> > Sent: Thursday, November 13, 2014 10:02:13 PM > Subject: [RBASE-L] - RE: On Row Entry EEP > > > What is happening is the component of the ROW that you are on has > FOCUS, so when you ENTER a new OTHER row, the getproperty command of > the onRowEntry EEP is retrieving the value of the component that has > FOCUS. > > > It is the timing of the events that is screwing you. > > > When you f8 between rows you could just have the same custom form > action that fires for each of the components you are likely to f8 > between, which should work for this scenario > > > However if you ABANDON the use of f8 and use the DB Navigator control, > everything will work as you expect. > > > Try it.. > > > Again, it is the timing of the events that is screwing you. > > > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] On Behalf Of > > [email protected] > > Sent: Thursday, November 13, 2014 5:23 PM > > To: RBASE-L Mailing List > > Subject: [RBASE-L] - RE: On Row Entry EEP > > > > Thanks, > > Copied and pasted the your code into the table's ON ROW ENTRY eep and > > changed the component ID name to the one on my form. > > > > (This form does not have a grid or scrolling region. Simply DB Edit > > controls placed > > on the form. The eep is in the form table on row entry eep.) > > > > Started the form and the pop up listed the correct value for the > first > > row along with the text message. > > > > Hit F8 (Next row) and the pop up displayed but the .vtext value did > > not change. (It should have) Hit F8 (Next row) again and the pop up > > displayed with the vtext changing to the value of the previous row > > (row > > 2) Hit F7 (Prev. Row) and the pop up displays with the vtext value of > > row 3. > > > > Same scenario as I was seeing before. Not sure why your system is > > different but alas it seems to be. > > > > Thanks anyway. > > > > Sincerely, > > Bob > > > > ________________________________ > > > > From: "Byerley, Mike" <[email protected]> > > To: "RBASE-L Mailing List" <[email protected]> > > Sent: Thursday, November 13, 2014 3:41:58 PM > > Subject: [RBASE-L] - RE: On Row Entry EEP > > > > > > Bob, > > Have you properly defined the variables to be filled from the > > GetProperty command BEFORE using them with the getproperty command? > > > > > > > > I can assure you you CAN get the value of a componentID in the > > onRowEntry EEP of a table. > > > > > > Here is my EXAMPLE: > > > > > > > > set var vTEXT TEXT = Null > > Getproperty dbeMainName TEXTVALUE 'vText' > > set var vMsg TEXT = (.vText & 'On Row Entry Fired') Pause 2 using > > .vmsg Return > > > > > > > > Even though the variable vText was defined JUST prior to its usage > for > > the example, I normally [and good practice] define ALL variables in > > the onBeforeStart eep. > > > > > > > > > > > -----Original Message----- > > > From: [email protected] [mailto:[email protected]] On Behalf Of Bob > > > Thompson > > > Sent: Thursday, November 13, 2014 4:22 PM > > > To: RBASE-L Mailing List > > > Subject: [RBASE-L] - RE: On Row Entry EEP > > > > > > It seems to be the GetProperty command. Using the exact same code > > > only removing the GetProperty and going back to the old style of > > > "Setting a variable equal to the column" in the expression builder, > > it works like > > > it always has. I was looking at using the more current > GetProperty > > > but it evidently is not meant for use in an on row entry eep. > > > > > > Bob > > > > > > Sent from my iPod > > > > > > On Nov 13, 2014, at 3:01 PM, "MikeB" <[email protected]> wrote: > > > > > > > Bob, > > > > > > > > I can verify that the EEPs in the current build are firing WHEN > > they > > > should: > > > > > > > > Put > > > > > > > > Pause 2 using 'On Row Entry fired' > > > > Return > > > > > > > > In the on row enter eep > > > > > > > > And > > > > > > > > Pause 2 using 'On Row Exit Fired' > > > > Return > > > > > > > > In the row exit eep > > > > > > > > > > > > You will see that they fire correctly, so then you can conclude > > that > > > you are not populating your variables when you think. > > > > > > > > When you trace, what is the value of vCompIDValue? Is it one of > > > > the > > > expected values? > > > > > > > > Also, you might just for S n G, place PROCESSMESSAGE before the > > > RETURN just in case the form repaint is waiting for something > else... > > > > > > > > > > > > > > > >> -----Original Message----- > > > >> From: [email protected] [mailto:[email protected]] On Behalf Of > > > >> [email protected] > > > >> Sent: Thursday, November 13, 2014 3:40 PM > > > >> To: RBASE-L Mailing List > > > >> Subject: [RBASE-L] - On Row Entry EEP > > > >> > > > >> OK, I probably am missing something but..... > > > >> > > > >> 9.5 Extreme latest build > > > >> > > > >> Form > > > >> > > > >> Table Settings > > > >> > > > >> On row entry eep: > > > >> > > > >> GETPROPERTY item_operation TEXTVALUE 'vCompIDValue' > > > >> > > > >> IF vcompidvalue = 'Moulder' THEN > > > >> PROPERTY knife VISIBLE 'true' > > > >> > > > >> ELSE > > > >> IF vcompidvalue = 'Emboss' THEN > > > >> PROPERTY embossdie VISIBLE 'true' > > > >> > > > >> ELSE > > > >> PROPERTY knife VISIBLE 'false' > > > >> PROPERTY embossdie VISIBLE 'false' > > > >> ENDIF > > > >> ENDIF > > > >> > > > >> > > > >> RETURN > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> The above data fields turn visible only when I leave the row, > not > > > >> when > > > >> > > > >> I enter it. I cut the above code out of the on entry eep and > > > pasted > > > >> into > > > >> > > > >> the on exit eep. It behaved exactly the same. > > > >> > > > >> > > > >> > > > >> I placed the variable vcompidvalue on the form to view and sure > > > >> enough, > > > >> > > > >> it's value does not change until leaving the row. Either the > on > > > entry > > > >> eep > > > >> > > > >> is not firing on entry or the values are not being refreshed > > > >> until leaving. > > > >> > > > >> > > > >> > > > >> I tried RECALC VAR in the EEP but no avail. > > > >> > > > >> > > > >> > > > >> Suggestions????? > > > >> > > > >> > > > >> > > > >> Thanks, > > > >> > > > >> Bob > > > >> > > > >> > > > > > > > > > > > > > > > > >
