Karen, If I need on exit field eep and it's the last editable field in the row in a region, I place a dummy variable edit field with a width of 0 to get the eep to fire. EX: set var vspoof text=.vspoof defined in the form variables. Place the variable so it gets the last tab in the row. In an on field entry eep in the dummy variable edit field I put a command to skip to the next row. Works for me. Bill Eyring
_____ From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Friday, January 15, 2010 11:37 AM To: RBASE-L Mailing List 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
