"inefficient" compared to what? And Inefficient measured how? And is said Efficiency necessarily the significant software quality attribute when up against competing attributes such as Maintainability, Reusability, Robustness. Of course, there's no single right answer. I'm just being curmudgeonly.
So, John, you often have to take things very very far before things get bad. Virtual fields are very very nice. (except for that EXTRACT() instead of var<fld> business mentioned earlier today. Now I'm being curmudgeonly again.) cds -----Original Message----- From: Drew Henderson John, Never tried to see how far it would go..... The real issue is inefficiency....each virtual field requires an additional read from the dictionary in which it is located. Doing this for every item in a report, you can see where the overhead makes chaining virtual fields inefficient. Drew Aherne, John wrote: >Hi All, > >Is it a bad thing when a virtual field references a virtual field in >another file, which calles a sub-routine to retrieve values from yet >another file? Does that even make sense? > >If not, how far could one take that before things do get bad? > >Thanks, > John ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
