Why not use TempVars instead. Adam would want it that way?
Access Developer 5 - Create a Global Module, Access Developer 6, Access Developer 8 - Create a Global Public Module. Access Devloper 11 (Universal Dialog Box), Accesss Devloper 12 (Universal Dialog Box 2 - Global Varialbes), Access 28 Comvert Code to Global Mod.

Thanks Jeffrey. I will take a look at those lessons.

John

Global Module

Thank Raymon - That show me which less to run. Very helpful

The quick answer thanks to ChatGPT:
https://chatgpt.com/share/68c4a517-da20-800e-a30c-ecdc96dc19ea

Now, before you get too far, you may want to map out your global modules.

I use a number for each application module (accounting, sales, etc.) that I create. Three (3) is dedicated to developer code, while four (4) is for the Universal Application (names, addresses, etc.)
For example, here are some of my names of global modules in the ADS:
mod_3_DateTime, mod_3_Form, mod_3_Numb, mod_3_Report, mod_3_String, mod_3_Translate, mod_3_Univ, mod_3_Util
mod_4_Univ
In each global module go procedures that are specific to what the name implies.