Understood. it is not a hard one and I can re-write this code to make it work in OpenBD. Thanks for the quick response. :)
Allen On Apr 1, 2:42 am, "Alan Williamson" <[email protected]> wrote: > Absolutely and I thought that was indeed a perfect example of where you can > work around it. The point is that you are making the decision instead of > making the engine do double guessing /every/ time a string is used for a key > > Hammer the crap out of performance. > > -- > http://alan.blog-city.com/ > > > > > > > > -----Original Message----- > From: "Peter J. Farrell" <[email protected]> > > Sender: [email protected] > Date: Fri, 01 Apr 2011 01:39:41 > To: <[email protected]> > Reply-To: [email protected] > Subject: Re: [OpenBD] caller[attributes.rtnVar] doesn't exist. > > Alan Williamson said the following on 04/01/2011 01:37 AM: > > So for us, this is not a bug, but a designed behaviour of the engine. > So just to follow up, you can at least use the workaround if you want > that desired behavior using Evaluate(). BTW, evaluate() is very useful > in certain circumstances such as this case. > > .pjf > > -- > Peter J. Farrell > [email protected] > [email protected]http://blog.maestropublishing.com > Identi.ca / Twitter: @maestrofjp > > -- > official tag/function reference:http://openbd.org/manual/ > mailing list -http://groups.google.com/group/openbd?hl=en -- official tag/function reference: http://openbd.org/manual/ mailing list - http://groups.google.com/group/openbd?hl=en
