Hi Gregory,
>Although I have not tested this. One could expect that the right side is only evaluated once, that would be the smart thing

That is what I thought until I searched for some of the reasons of a VERY slow starting app. They had bound all their combos to views opened (all at start for verification code) in the biz tier. In the where clause there was a reference to this.parent.parent.oStatic, which gave loading times of 70 to 240 ms - not a horrible thing for one view, but nothing to be proud of when loading between 20 and 50 views. Just somedirty slight of hand generating and shielding memvars and moving the properties into them drove the loading times down to 15 to 90 ms, gaining between 2 and 5 secs depending on the form that was started. Since that time I make the effort to buffer as much as possible before running lines potentially accessing N records.

>I have added one object to _screen (the App object) and almost everything is in there including Environment (Datasession for form.load), menu, database object, toolbar refs and much more). The nice things is, that when the object is destroyed, it closes that database, menus, etc
>So, as to the minuscule object redirection time, it's a trade off, and I'm accepting it

Usually that is my approach as well, and then I create a private object reference into to the object of that structure I need to access often in a tuple of routines. If THAT one line is too heavy, something is wrong with the design. But here I hesitate to use that approach, since code triggered and with redirected error handler is perhaps not stable enough and might leave some dangling references somewhere.

regards

thomas