Arthur Fuller
fuller.artful at gmail.com
Wed Dec 31 10:21:58 CST 2014
My little take on this is: a) none of these approaches will be portable to any other FE; b) it's always helpful to encapsulate your logic in a function rather than a TempVars variable; c) sad as I am to say this, it appears from Microsoft's behavior that Access has become an abandoned child. I write this with great sorrow because I have invest years and years in this technology, but I have made this mistake before, and subsequently licked my wounds and moved on (you want details? I got them: I spent more than a year writing a book about CA-Visual Objects, which was so buggy it was almost impossible to write about, and the result was I made a bad choice and suffered loss of income for about a year, give or take a month.) Back to the topic at hand. Expect that Access will soon be abandoned by MS. All the evidence for this thesis is their abject failure to provide any new tools for developers, since, wait, let me guess, 2007? Don't get me started! Not to sidetrack this conversation, but just to add that MS's abject failure to deliver for developers is why I moved to Alpha Anywhere. That firm has vision; MS, imo, does not. So, Brad, my advice is to refrain from TempVars and instead use Functions, and even better, Static Functions. Not only do they work perfectly within Access, but they also provide you a portable way out of Access and into new platforms (yeah, I champion AA but am also cool with good old friends such as PHP and a couple of other JS libraries.) On Wed, Dec 31, 2014 at 9:40 AM, Brad Marks <bradm at blackforestltd.com> wrote: > All, > > I have just started to experiment with TempVars. > > I am curious if there is any advantage of using TempVars instead of > Functions in queries (in Criteria). > > Thanks, > > Brad > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > -- Arthur