RE: Lynda's email from 8/22/2002 at 7:31pm

1. Patched FA6300.dbl for problem when life values for each depreciation
   method are different.

2. This is one I thought you could explain to me; however, since you asked
   I spent a couple of hours looking at the calculation program and came
   up with the following.  The depreciation year is based upon 360 days in
   the code.  Therefore, when the year has 365 days, it cuts off the depr
   at day 360 (usually around Dec 25 or 26).  Then when it computes the
   depr for Jan 31 of the next year, it has to do a catchup calculation and
   is actually using a 36 or 37 day period which makes the depr amount
   larger than other months.  I also found in the code where if the last
   depreciation date of the asset is not the one on file, it actually
   calculates the elapsed days but if it is the same it uses 360/12 or 
   always 30 days.  This is why on the comparison report the amounts in the
   first year vary from month to month depending on the number of days in
   the month, but in subsequent years the amounts are the same for all months
   (except Jan) since it is always using 30 days.  I can not find anything in
   the "2000 U.S. Master Tax Guide" as to why this should be done or why the
   year is always based upon 360 days (except that when quarters are required
   for calculateions, it makes each quarter an even 90 days).  I tried an
   experiment in the code to make it always calculate based upon actual
   days instead of 30 in subsequent years, and it seems to be more accurate
   against the tables in the Tax Guide.  The code I am sending to you this
   time leaves the experiment in place.  If someone knows why the program
   was using 30 days after year 1, and it is the preferred way, let me know
   and I will reverse the code back to what it was.

3. Patched FACALDP.dbl to scale auto calculations down by 100. 
 
