The SQL database used by Captools/net is a "relational" database, meaning that it imposes requirements for minimum data and unique date in each data record and also imposes certain relationships between data records.

 

For example, the Captools/net "client table" record "Client Id" field must contain a value that is unique to that record, i.e. no other client record may contain that Client Id value.  Additionally, the database relational constraints requires that a Captools/net "account" record's Client Id field must contain a Client Id value that exists in a valid "client" record.  This means that in order for you to enter a new account record, you must enter the client record for that account before you can enter the account record.  Likewise, you may not enter portfolio records until a corresponding account record has been entered into the database.  

 

Once a top level record, such as a client record has been entered into the database, that record may not be deleted without deleting all of the dependent lower level records.  Typically Captools/net will prompt you to advise when a dependency requires the addition of higher level records, or when it will result in the removal of lower level records.  Accordingly you do not need to learn or memorize Captools/net's database relationships, merely be aware that they exist.

 

The definition of the table fields and the interrelationship between the tables and the fields are contained in the database file itself.  Captools/net is shipped with a "skeleton" database file containing the database relationships, plus some sample data.  Although the sample data may be removed, you must use this database file, named "CaptoolsDB.mdf" in order obtain the proper database table definitions and relational constraints.