title: Using Global Constants to store environment variables
body: <p>I'm creating an add-in for Microsoft Excel and I'm using a module to store variables (which do not change during runtime) which are accessed by classes and other modules in the app. This is a more convenient way of hard coding values which I may have to find and replace at different points in the development cycle.</p>
  
  <p>The variables are things such as the app version, or the workbook password:</p>
  
  <pre><code>Option Explicit
  Option Private Module
  
  Global Const APP_ID = "XXY"
  Global Const APP_VERSION = "1.00"
  Global Const WORKSHEET_PASSWORD = "s0Me_pa$$w0rD"
  Global Const DATA_TABLE = "tblStockData"
  Global Const FORM_DEFAULT_VALUE = 200
  </code></pre>
  
  <p>I was wondering if anyone can tell me if this is bad practice and if so, what a better course of action would be?</p>