If you are upgrading from a previous version just replace the old
QRDB.EXE and QRDBMGR.EXE files with the new ones in this package.
A file that was added in ver 4.0, QRDBLang.DBF is also required.
If you use the Fossil version of QRDB, it is the file called QRDB_fos.Exe,
depending on your setup you may have to rename it QRDB.Exe. Earlier
fossil versions were in a seperate package and were called QRDB.Exe.

            --------       ATTENTION      --------
When run in local mode or stand-alone full access to all features is
given and levels do not apply.


QRDB is being supplied is being supplied in both Non-Fossil and Fossil
versions. The fossil version is in QRDB_FOS.EXE and is included. Some
BBS systems running under a Fossil have found that the non Fossil
version won't work with their system. I run a QuickBBS system and use
the Non-Fossil version. I have had reports from Max and RA sysops that
required the Fossil version. The Fossil version won't allow you to
hang up on a user, but you can always use that button on the modem.

The error message "Cannot execute QRDB.EXE" means that the program
does not have enough memory to operate in. You need at least 400k.

If you get the Error message "QRDB.Dat not found or Corrupt", make sure
you have the environment variable set, before looking for other
problems. Example QRDB=C:\QRDBDIR set it to the directory that QRDB is
located in.

Earlier 3.x versions of QRDB had a problem that sometimes left two keys
to the same type 3 record when a keyfield was edited using QRDB. The old
key and the edited key both pointed to the edited record. If you have
duplicate keys you will have to rebuild the index using the QRDBMgr
program to get rid of them. First use the function: (E)rase QRDB
Index/Data then (B)uild Type 3 DB Index.

The following info was added to the docs, you may have nissed it A
numeric field as a key may have problems indexing. Depending on how the
key field was input. dBase, dBuddy or QRDB. It is suggested that you
don't use a numeric field as a key unless all input is via one system.

If you are updating from Versions of QRDB prior to 3.x read the following.

If you have type 3 Database files, use QRDBMgr to check Security levels.
Add, Edit and Delete features have been added to the type 3 DataBase,
and security level fields in QRDBMgr have been expanded to control
access. One other thing on the type 3 DataBase field codes in QRDBMgr
have also been changed to N,O,R and K. The old (D) code will be
interperted as (O) in any existing files.

                   (N)/A                                               
                   (O)pt                                               
                   (R)eq                                               
 Name      Typ Len (K)ey  Display Label                   Line Col     

The following is an answer to a couple of Frequently asked questions

1. QRDB looks in the directory it is run from for, DorInfo1.Def or
Door.Sys. So it should be run from the directory your system puts
Door.Sys in. Door.Sys shouldn't be put in the QRDB directory, because if
it is you can only run one node as the QRDB directory can contain only
one copy of Door.Sys.

2. QRDB uses the following lines from Door.sys

1.  Comm Port - COM0: = LOCAL MODE
2.  Baud Rate
10. User Full Name (First and Last)
11. Calling From (City, State)
15. Security Level
19. Minutes Remaining THIS call
20. Graphics Mode - GR=Graph, NG=Non-Graph
21. Page Length




