Declaring Variables
in [Programming]
|
From: BlairH on 4 Jun 2010 09:12 I'm either horribly confused, or old age is taking its toll. But there seems to be too many options for declaring variables and I;m having trouble figuring out the best way for declaring variables. Tell me if I have it straight: variables declared at the top of a module are shared within all procedures in the module, decalred within a procedure/function are available to only that procedure/function variables declared Public are available to all modules - in this workbook only or all workbooks? - so these should be declared at the top of a module? variables declared Static retain their values between procedure/function calls - declare in a procedure/function variables do not retain their values once hte code stops and control returns to the user, so if you want to retain values you need to stor ethem in a cell in the spreadsheet Sound right? Thanks!
From: Jackpot on 4 Jun 2010 09:32 Does these articles help. http://www.ozgrid.com/VBA/variable-scope-lifetime.htm http://www.java2s.com/Code/VBA-Excel-Access-Word/Language-Basics/Const.htm "BlairH" wrote: > I'm either horribly confused, or old age is taking its toll. But there seems > to be too many options for declaring variables and I;m having trouble > figuring out the best way for declaring variables. > > Tell me if I have it straight: > > variables declared at the top of a module are shared within all procedures > in the module, decalred within a procedure/function are available to only > that procedure/function > > variables declared Public are available to all modules > - in this workbook only or all workbooks? > - so these should be declared at the top of a module? > > variables declared Static retain their values between procedure/function calls > - declare in a procedure/function > > variables do not retain their values once hte code stops and control returns > to the user, so if you want to retain values you need to stor ethem in a cell > in the spreadsheet > > Sound right? > > Thanks!
From: Jackpot on 4 Jun 2010 10:03 I notice the specific question marks only now..Answers within brackets - in this workbook only or all workbooks? (In this workbook) - so these should be declared at the top of a module? (Yes) variables declared Static retain their values between procedure/function calls - declare in a procedure/function (Yes) -variables do not retain their values once hte code stops and control returns to the user, so if you want to retain values you need to stor ethem in a cell in the spreadsheet Sound right? (Variables declared on top will retain their values all through that Application session OR until Excel application is closed (assuming they are not initialised within code)) "Jackpot" wrote: > Does these articles help. > > http://www.ozgrid.com/VBA/variable-scope-lifetime.htm > http://www.java2s.com/Code/VBA-Excel-Access-Word/Language-Basics/Const.htm > > "BlairH" wrote: > > > I'm either horribly confused, or old age is taking its toll. But there seems > > to be too many options for declaring variables and I;m having trouble > > figuring out the best way for declaring variables. > > > > Tell me if I have it straight: > > > > variables declared at the top of a module are shared within all procedures > > in the module, decalred within a procedure/function are available to only > > that procedure/function > > > > variables declared Public are available to all modules > > - in this workbook only or all workbooks? > > - so these should be declared at the top of a module? > > > > variables declared Static retain their values between procedure/function calls > > - declare in a procedure/function > > > > variables do not retain their values once hte code stops and control returns > > to the user, so if you want to retain values you need to stor ethem in a cell > > in the spreadsheet > > > > Sound right? > > > > Thanks!
From: BlairH on 4 Jun 2010 10:04 Those article sdo help. Thanks. "Jackpot" wrote: > Does these articles help. > > http://www.ozgrid.com/VBA/variable-scope-lifetime.htm > http://www.java2s.com/Code/VBA-Excel-Access-Word/Language-Basics/Const.htm > > "BlairH" wrote: > > > I'm either horribly confused, or old age is taking its toll. But there seems > > to be too many options for declaring variables and I;m having trouble > > figuring out the best way for declaring variables. > > > > Tell me if I have it straight: > > > > variables declared at the top of a module are shared within all procedures > > in the module, decalred within a procedure/function are available to only > > that procedure/function > > > > variables declared Public are available to all modules > > - in this workbook only or all workbooks? > > - so these should be declared at the top of a module? > > > > variables declared Static retain their values between procedure/function calls > > - declare in a procedure/function > > > > variables do not retain their values once hte code stops and control returns > > to the user, so if you want to retain values you need to stor ethem in a cell > > in the spreadsheet > > > > Sound right? > > > > Thanks!
|
Pages: 1 Prev: Search Macro or VB script Next: Excel template similar to MS Money less investments? |