A
alex.wiese.pulse
Guest
[quote user="Lieven De Foor"] I would never depend on the availability of buffers outside a FOR statement. But inside the FOR, since this is an inner-join, I would expect both to be available. Can you rewrite using a (dynamic) query and get the first result? Then both should be either available, or both not... [/quote] Hmm this is a pattern we use extensively in our application (rightly or wrongly); we haven't had an issue with it before and didn't expect it to change in v12. Inside the FOR will never be executed if there is no matching security record. On v11.7.5 and earlier the first buffer is available (even when there is no matching security record), and in v12.1 with "server side joins" disabled it's also available, so it appears to be a bug in "server side joins", or at the least a breaking change. If it's intended behaviour with the new "server side joins" then we will have to rewrite a lot of code [:|].
Continue reading...
Continue reading...