If I'm following what you are saying here, I think I already do that. I
store amount paid, charges covered and in some cases the rate things cost at
that time. I also have several functions I use in place of doing it over and
over again such as getting the last day of a month etc.


PC Datasheet wrote:
Joe,

Another point that you might consider ---

Your case is a good example of storing a calculated value rather than
calculating it on the fly. Say you have ExtendedCost = Cost * Sales
Tax Rate. Since Sales Tax Rate will vary, it would make things
simpler to store ExtendedCost each time rather than calculate it on
the fly.


"Joe Cilinceon" wrote in message
...
John Marshall, MVP wrote:
I guess as a failed gas station attendant, you did not excel at
reading. Joe originally asked for "a variable that will last for a
session.". Global variables will do this, but there are caveats as I
mentioned..
John... Visio MVP

Actually John I asked for the best method to set default values in an
application, be it as a public variable or Lookup Table. I didn't
know and really still don't know which method will work best for my
needs. I gotten 2 different methods of doing what I want and will
try both before deciding. It really amounts to about 5 or 6 default
values, such as sales tax rate, late fee charges, lock cut fee,
admin fee, lien fee and nsf check fee. I use these charges thru out
the application for calculations and it would be nice not to have to
rewrite these values in code every time they change. I hope that is
clearer. --

Joe Cilinceon

--

Joe Cilinceon