NOW IT'S ON!! FLAME WARS!!!

jk. You're probably right, there are better naming conventions but I haven't used true global variables much. Most of my variables that are referenced in multiple functions are used within the same module, so I've dubbed them my globals as they cover the whole globe of that module. (digging the whole deep enough?) I should rethink the strategy I'm sure... but up until now nobody has called me on it as not many people analyze my VBA... they just laugh because I'm not in .NET or Java.

I suppose from now on I'll have to start using m_variable for module level variables... or something like that. Sooner or later I'll become an expert and then 2010 will change everything and I'll be a beginner again.
(It hasn't really 2010 is fun. It even allows you customization of the ribbon like the pre 2007 custom toolbars, I think everyone will like it) But I digress. I have no valid excuse for poor naming conventions.
Job security maybe?