Karen, I ran into that problem a couple of years ago. The scrolling region was simply the best tool to use but when the user is using F7 and F8 to go between rows I needed it still to calculate properly and the row exit was not the place to do it in this case.
So I basically created a SKIP -1 and then a SKIP 1 (it's a little more complicated than that) in the field ON ENTRY eep to get the desired results. Jan -----Original Message----- From: [email protected] To: [email protected] (RBASE-L Mailing List) Date: Fri, 15 Jan 2010 11:36:37 EST Subject: [RBASE-L] - Opinions on regional eeps? Just looking for opinions, because I just ran into this again when looking at an older app. In a form with a region, it has always been the case where if you have an "exit field" eep, it will not evaluate if you go from the field in that row directly to the same field in another row. IE: you either F8 right from the field, or click into the row beneath it, without ever leaving that field. This is because RBase doesn't think it has left the field, because it's still in the same column. (At least I think that's the logic.) Ran across a case where we had some inventory calculations going on when leaving the field, and sometimes they weren't working. When I saw the calc was on field exit level, I knew what was happening. So I had to change the eep to "row exit" level instead. It works fine there, but there are times when I could use a field exit instead so that I can check something before they go onto another field in that same row. This is an original RBase behavior, and I'm not even sure they could change it if we wanted them to. So I'm just curious if everyone out there never uses field exit eeps on a regional form ... Or do you assume the user won't click into the next row ... It's a slow day ... Karen
