M
Mike Fechner
Guest
IMHO a good practice is to DEFINE BUFFER Customer FOR Customer in each and every method (that requires that buffer). Sent from Nine Von: dbeavon Gesendet: 10.06.2017 9:20 nachm. An: TU.OE.Development@community.progress.com Betreff: RE: [Technical Users - OE Development] Seriously???!!!??? Strange OOABL behavior Update from Progress Community dbeavon Are we sure it is a bug? OE's OO classes have a number of oddities in the way that various data types are scoped. It would be nice if the scope of some things like temp-tables and, in this case, buffers would be limited to the context of a method. Unfortunately that is not the way classes work. I'm told it is for legacy reasons. The scope of your buffers and temp tables is at the class level, like an instance member. For example, I've often run into issues where a buffer will be moved with FIND in one method call, and then another nested method call will move the buffer again, so that when control returns to the outer method, the buffer is either lost or not on the same record as it was when the inner method was started. Because buffers have class-level scopes instead of method-level scopes, it is possible that this behavior is by design. The only way the compiler could easily tell that you didn't intend to actually use the customer buffer is if record buffers were scoped at the method level. View online You received this notification because you subscribed to the forum. To unsubscribe from only this thread, go here . Flag this post as spam/abuse.
Continue reading...
Continue reading...