===== Dealing with Error-messages =====
==== Access Denied =====
Depending upon the circumstances, the inability to gain access to a database may be reported as **DOS Error 5** or **Runtime Error 105**.
The usual reason is that
the database has been copied from a CD-ROM, perhaps to recover a back-up copy. You can use Windows Explorer or MS-DOS
commands to correct this.
=== Remove the Read-only Attribute with Windows Explorer ===
  - Navigate into the relevant database folder on your hard disk.
  - Select all the files, by pressing keys Ctrl+A or otherwise.
  - Right-click on the selected files and choose **Properties**.
  - Clear the read-only box, by clicking on it.
  - Click on **OK**.

=== Remove the Read-only Attribute with DOS Commands ===
  - Get an MS-DOS prompt
  - Make the database folder current, e.g. by typing the command <code>cd \pedgree\elton.ped</code> and pressing Enter.
(Use the appropriate database name in your command.)
  - Type the command <code>attrib -r *.*</code> and press Enter
  - Type the command <code>exit</code> and press Enter to close the prompt window.

Another reason for this message is that you have tried to open the database with both //Pedigree for DOS// and //PediTree// (or two
instances of one of these programs). You **cannot** do this.

==== DB32 Fatal Error =====
When running PediTree, you may encounter the following example message (or something similar)\\

{{:faq:db32err.gif|}}

The appearance of a message-box like the above with the same heading is often due either to a missing file or
to a fault in your database. From PediTree version 3.330 (February 2010), missing or inaccessible files
should be detected before DB32 is involved, so these messages are probably due to a database fault (the example above is one such). However, if you try to use PediTree to open a database that is already opened in //Pedigree for DOS//, you will receive an **Access denied** error in this form.  This is easily corrected: close //Pedigree for DOS// and try again.

The quick fix for other causes is to restore your database from a recent back-up copy. Alternatively, you may prefer
to repair the database, if possible.  Instructions for this are available [[utilities:dbutil|here]].