home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Datafile PD-CD 3
/
PDCD_3.iso
/
pocketbk
/
utilsr
/
s3abank4
/
README.NEW
< prev
next >
Wrap
Text File
|
1995-05-07
|
3KB
|
66 lines
S3ABANK V1.4e - READ.ME file
----------------------------
Welcome to my Home Accounts V1.4. Please note this file is for New
Users only. Users of V1.3 should read README.V13
This is a fairly complex program, so I would encourage you to read
the instructions and work through the tutorial.
However, if you still insist on flying blind:
1. Put S3ABANK.APP in your \APP\ directory
2. Put the .OVL files into a \APP\BANK\ subdirectory
(S3ABANK1.OVL, S3ABANK2.OVL and S3ABANK3.OVL are ESSENTIAL !!)
(The remaining Overlays provide on-line Help - S3ABANKH.OVL -
and extra modules as required - so far, Budget, Planner, Shares,
Petrol, House Contents and Utility, others to come later)
3. Install (PSION-I) and go for it !!
If you do get a problem, PLEASE read the full instructions. I have yet to
be asked a question that wasn't already explained in the instructions !!
Warning
-------
There have been two reported cases of a program crash with V1.2,
involving loss of data, both caused by operating when the data disk was
getting very full. The problems which caused these crashes have been
fixed, but this is such a complex program, I cannot guarantee there aren't
any more more lurking in the background. I would highly recommend that
you keep backups of your data on a PC, or if that is not possible,
utilise the BACKUP <PSION-B> option within the program to keep a spare
copy of your data somewhere else on the disc. I have to say that I use
BOTH methods, and I wrote the program !!
Frequently Asked Questions (FAQ)
--------------------------------
So Far, only one:
"Why is there a limit on the number of transactions ?"
Because the transactions always need sorting in date order, I decided to
load them all into memory. This necessarily led to a limit on the number
of transactions per account. Remember, the idea of the program is to hold
in an account only those transactions that haven't been reconciled against
a written statement. Once this has been done, they can be archived in a
separate account which can hold unlimited transactions, but they cannot
subsequently be altered. I started with 50 transactions to save memory,
reasoning that this was a reasonable number for a month's transactions in
an account, but soon realised that 100 was more realistic, so that was
changed for future versions.
That actually reminds me of another point:
Because all users are different, I store the maximum allowable number of
accounts, transactions, standing orders etc... as variables. Therefore,
changing the limits simply means adjusting the variable allocation and
re-compiling. Therefore, within reason, I can provide individual versions
of the program for anyone with special requirements.
All other comments (and registrations, See REGISTER.TXT)
still gratefully received.
Alan Richey