12.  TROUBLE SHOOTING

It is best to run Paradox 4.5 from Windows using the PDOXDOS.PIF file. This seems to clear
up many memory allocation problems.  When running Paradox 4.5 on a machine with 8 or
more megabytes of RAM, use a command line option -extk 4096.  For example, a Windows
command would read: PARADOX -EXTK 4096 SHIMS.  This forces use of no more than 4
megabytes, which should leave plenty of memory for Windows 3.1 or Windows 95.  It is
required that Paradox 4.5 use a ASCII sort order.  If you used a different sort order when
Paradox 4.5 was installed, call Mike Callahan.

A common error occurs when users try to print out reports for incomplete data sets. The
program displays an error message box.  SHIMS was designed to account for certain missing
data, but assumes that the necessary data will exist.  For example, to print out an E-19A, 
there must be a gage assigned to that location since all river gage locations should 
have some sort of active river gage, i.e., a river gage with no ending date.  In most cases, 
errors occur when you have typed in a little bit of information and cannot wait to see the 
new report. The solution is to type in all known data BEFORE attempting to generate reports.

Paradox will not allow most database actions to occur while editing tables.  This means that
while a table is being editing or viewed, most menu bar commands bar will be inactive.  Click
on done in the speed bar and then the desired command.  This version of SHIMS does not use
memo fields, thereby eliminating potential problems associated with memo fields.

Paradox and SHIMS occupy a large portion of disk space.  Make sure there is ample space on
the disk at all times.  Corruption of database files is possible if the user runs out of 
disk space.  Paradox and SHIMS should reside in different directories.  This is very important 
since the number of files in SHIMS now exceeds 100.

If an error does occur, Paradox will stop SHIMS and present the user with an error message
box. Write down the error message and then click on OK.  Next, you see the Debug Quit
menu.  Most times the user should select Quit, and then check the tables in regular Paradox
using the View menu.  The brave user can use the Paradox debugger to try to determine the
error.  In either case, there is little chance of data being lost.

THE NEED FOR FREQUENT BACKING UP OF THE DATABASE CANNOT BE OVEREMPHASIZED.  Many problems 
with earlier versions of SHIMS could have been minimized if the database had been backed up.  
The database should be backed up after any significant editing has occurred.  Even if your 
office routinely backs up your entire system, it is an excellent idea to maintain a backup 
of your SHIMS database yourself.  Many service hydrologist have learned this painful lesson by 
having to retype an entire database.  If the Backup command in SHIMS does not work, call Mike 
Callahan.  In every case in the past, problems with the Backup command have been easy to fix. 
Do not use SHIMS without the Backup command working.  When exporting and importing data 
between offices, use the same version of PKZIP and SHIMS since the database tables are 
compressed into one .ZIP file.