Power Tip: Maximize the use of TempVars in Access 2007 and 2010

re: Power Tip: Maximize the use of TempVars in Access 2007 and 2010

Access_Expert — Tue, 28 Sep 2010 14:09:50 GMT

David You are correct, there is no built in type checking, it is therefore up to the developer to maintain consistency in the code and use monikers such as str for String, lng for Long, etc. I look forward to your feedback once you start using 2007 or 2010, there many other great features you will enjoy, not the least of wish is the tab interface, which is my favorite. Kind Regards,

Juan ORIGINAL POST:

I've not done any A2007/A2010-specific programming yet, so have had no opportunity to try the TempVars collection, but my main concern is that you're sacrificing strong data typing of variables. There are a whole host of ways besides global or module-level variables to store data in memory in a way that will survive a code reset, and retain the virtues of strong data typing. My main concern is that if all TempVars are variants, what's to stop you from storing something of the wrong data type? I looked at the documentation on MSDN and could see nothing about that at all.

re: Power Tip: Maximize the use of TempVars in Access 2007 and 2010

Garry Robinson — Tue, 28 Sep 2010 05:58:58 GMT

From memory there is a maximum of 255 tempvars in a database. Tempvars are great in action queries TempVars!strAppName, especially ones that are used in exports (which fail when referencing form fields). Set them in code or a macro, plug them into the query and they magically turn up. Beats using functions for the same result.

re: Power Tip: Maximize the use of TempVars in Access 2007 and 2010

David W. Fenton — Tue, 28 Sep 2010 00:19:28 GMT

re: Power Tip: Maximize the use of TempVars in Access 2007 and 2010

Albert D. Kallal — Mon, 27 Sep 2010 17:41:43 GMT

Another long time workaround one can consider using a mde, or accDE. In a mde or accDE, then un-handled errors never re-set local or global vars. The other often not realized advantage of a mde/Accde is that un-handled errors don't cause the runtime edition to stop, or shutdown. In fact, your program just keeps on running without a problem. So, in addition to TempVars, one can consider using a mde, or accDE as another means to give you bullet proof variables that don't re-set on un-handled errors. This also means that class object variables also retain their values, and again do so regardless of errors occurring. However, in cases where you can't or are not using a mde/accDE, then TempVars are great use case. And, your tip and point about being able to use TempVars in a query without a function is even more useful. In fact, I am going to adopt this practice in both accDE and accDB applications for the future. Thanks for sharing this with us. Albert D. Kallal (Access MVP) Edmonton, Alberta Canada