Configure, Program Settings...
Require Strong Passwords
When this option is enabled, DonorQuest will only allow users to use strong passwords which must contain at least 8 characters, a mixture of uppercase and lowercase letters, at least one digit, and one special character such as $, !, @, #, etc.
Enable Enhanced Find
This program setting is on by default and allows you to search within fields while doing a Find. If turned off you will still be able to search your database with the Find across fields, however DonorQuest will then only search from the left of a field rather than from within a field. Most organizations will want this switch turned on since the searching capabilities are more advanced, but for those organizations with large databases (over 200,000 donors or so) and slow in-house networks it may prove more efficient to have this switch turned off. Basically just try having it on first and then only turn it off if you need to. The online version of DonorQuest should always have this setting enabled since it essentially has no limits on performance or database size.
Maintain Best Year Totals
This should always be enabled for the online version of DonorQuest. If you are using DonorQuest in-house on a slow network, then disabling this feature will improve data entry performance when adding or editing donations.
Allow Local Report Cache
This applies only to the in-house version of DonorQuest running across a network share. When using a large database across a local area network connection, it is recommended your network administrator enable the DonorQuest Server Component for the best query and report performance. However, if your server does not support doing this because it is not a Microsoft server, or it is a simple NAS drive, then enabling this local report cache is the next best method of enhancing performance. With local report caching enabled, DonorQuest will copy the most needed reporting data to each user's actual workstation and keep it up-to-date with what's on the server. Then, when a report is run, DonorQuest will use the local cache on each workstation for fast access to the data, instead of reading it all across the local area network connection. With this setting enabled, each user may then turn on or off caching for their specific workstations as needed under their personal settings. This may be necessary if a user's workstation is using a very old hard drive design, and processing reports across the network connection turns out to be faster for them.
Encrypt Database
DonorQuest is capable of encrypting your entire database while still providing full multi-user access. This feature is intended mainly for those still using DonorQuest in-house on a local file server. The encryption is seamless, so that everything in DonorQuest works just as you would expect for all features. This adds a layer of protection for your sensitive donor data, making your data appear as unreadable gibberish to any would-be thieves which either hack into your main file server over the Internet, or perhaps even physically steal it from your office. Without knowing a DonorQuest User Name and Password, there is no viable way a hacker could decrypt your data if you are running DonorQuest with encryption on. You may also uncheck the box at anytime to return to running in normal unencrypted mode. The only downside of running with encryption on is that it will slow DonorQuest performance slightly, but only by about 10% on average. Any changes to your encryption preference will be processed against the database after you close the Program Settings dialog.
Run Integrity Checks
This applies only to the desktop or the in-house version of DonorQuest running across a network share. Database faults can never happen with the online version of DonorQuest. However, when running with the DonorQuest database on your actual computer, or on a file server across a local area network in your office, faults may happen if you have a power failure while DonorQuest is open, or if there is a fault on your local area network. Enabling this option will cause DonorQuest to prompt for a weekly integrity check. The check can always be declined if it is not a convenient time. If you are running on a super stable network or the local storage of your computer, then the weekly integrity check prompt can be disabled by turning off this setting. Integrity checks may still be manually run by clicking on System, Table Integrity, Check Only.
Run Index Maintenance
This applies only to the desktop or the in-house version of DonorQuest running across a network share. Like database faults, index faults may also occur if you are running on a less than reliable local area network environment. If this option is enabled, then approximately every month the last user logging off for the day will be prompted to run index maintenance. They may decline if it is not a convenient time, but the prompt will continue until the maintenance is performed. If you are running on a super stable network or the local storage of your computer, then the monthly index maintenance prompt can be disabled by turning off this setting. However, you can still manually rebuild the index files if ever necessary by clicking on System, Index, All Tables. Click the Yes for the confirmation prompt.
Run Local Backups
This applies only to the desktop or the in-house version of DonorQuest running across a network share. With this setting enabled, DonorQuest will prompt to run a local backup every week. Note that the backup is NOT a cloud backup. It is simply making a duplicate copy of the entire database on the same computer the active database is running on. This is useful if a user makes an accidental sweeping change to the database they need to reverse, but it does not take the place of a proper cloud backup, or a backup to a physically separate USB drive. Since the backup takes time and may be inconvenient, this weekly prompt may be disabled by turning off this option. Local backups may be run manually as needed by clicking on System, Run Local Backup. The online version of DonorQuest runs automatic nightly backups which are stored in a separate data center and kept for a full year. However, this local backup feature can still be handy if you are about to make a sweeping database change, and you need an up-to-the-minute backup to restore from if need be.