Updated 5/30/87


   This program is NOT public domain, however, it may be copied and
redistributed for nonprofit purposes as long as the built in title
screen is not removed.

---------------------------------------------------------------------------

	The following program is written in AmigaBasic (no moaning
please).  It's rather long but it is also fairly user friendly and
does what I think needs to be done with a checking account.  The
Check Tracker maintains a record of all checking transactions and
includes the capability of editing and searching all entries.  When
the time comes to evaluate the monthly statement the program will
assist in verifying that all balances are correct and in the event
of a problem it will run through all pertinant data for
verification.  Also, the program can handle up to 96 different
accounts (If that's not enough then don't call us....we'll call
you).

-------------------------------------------------------------------

STARTUP NOTES
~~~~~~~~~~~~~
	As I said before, this program is written in AmigaBasic.

	You should run the loader program first as Basic's default
memory allocation is insufficient to load the program.  The loader
will allocate some more memory then load the run the main program.

	I recommend putting the Loader and the Main program in thier
own directory.  Each account will require it's own subdirectory.  If
you like, you can create the subdirectories now or wait till the
program asks you to do so (you can multitask back to CLI or
WorkBench from the program as needed).

	When starting the program make sure BASIC is in the correct
directory.  From CLI you can CD to the directory then use the
following command:

RUN DF0:AMIGABASIC CheckLoader

From within basic you can set the directory by typing the following
in the OUTPUT window:

CHDIR "DFx:directory"

I was trying to set up the CheckLoader icon so that it started basic
from df0: but it didn't leave basic in the correct subdirectory.  If
anyone knows how to make this work, drop me a line.
------------------------------------------------------------------

	I'm really not sure how much documentation is needed to use
this program.  I will hit the high points and appreciate any
comments from users.

	At present, this program allows for 50 entries/month.  Drop
me a note if this isn't enough.

STARTING A NEW ACCOUNT
	When beginning a new account I recommend going back far
enough such that all checks have cleared.  If a check clears or is
lost from before the start of this program if can cause some
problems.  When entering new data, if a check being entered has
ALREADY cleared ust the status Old Check.

CHECK I.D. NUMBERS
	Check I.D. numbers are used at the time of statement
evaluation to determine which checks have been returned and which
are outstanding so be careful when entering these numbers.  Any
entry with a status of New check or Old check must have a unique
number.  Conversly the status identifiers of N and O should only be
used for checks.

FILE STORAGE
	The program stores each month as a separate file in an
accounts' subdirectory.  If you accidently type 6/5/97 instead of
6/5/87 when entering a date the program will be forced to create
12X10=120 files (1/ month).  Be very careful when entering dates.  I
have included some elementary date checking.  This is in the form of
a warning which can occur even if you do enter the correct date.

STATUS USEAGE
	Anytime money goes into the account you should use the
status Deposit or Interest (they are treated the same).  Money going
out (besides a check) should be logged as Cash.  If a check goes 4
months without being cashed the program will VOID it, recompute the
correct balance and provide a notice to this affect.

ENTERING DATES
	Dates can be entered in either of the following forms:

3-2-62
03/02/62

Also, the day entry is not always needed.  If this is the case, the
program will prompt for MM/(DD)/YY and you can simply enter:

3/62


------------------------------------------------------------------

	This is about it for DOC for now (I'm a rather lazy person).
I'm sure I've left out some piece of crucial information.  I have
tried to have the program check all user input for validity.  I'd
love to hear any ideas for improvments (although this program is
already inconviently long).

	I'm considering removing some of the sections where the
program asks the user (ARE YOU SURE).  Tends to get annoying after a
(short) while.  Drop me your ideas.

	I can be reached through the BBS's listed below.  Tell me
where you have problems and I'll spruce up the doc.

David Levin

People/Link - I.D. # OMS281
LAAUG line (213) 559-7367 - Send mail to David Levin