Version 6 release introduction

If you have already been using version 6.0 or later and are ready to install version 6.1.4, then skip to the bottom of this page and click the yellow "Upgrade Instructions" button. If you're new to version 6, then you may want to review this page for changes in version 6 from previous versions.


Important notes on new features:

AUTH CODE ONLINE LOOKUP -- It seems to be a common occurrence that people forget to enter their new authorization code when they renew their updates. This has become a support nuisance to constantly send people their codes again, so now Campground Master will prompt you to check online for your authorization code if it appears to be out of date, automatically updating it for you.

So, if you get a "not authorized" message after you upgrade and it asks you to check online for your new code, be sure to answer "yes". You can also do this later in Maintenance / Park Setup / Parks, by clicking the button at the bottom "Download updated code(s)".

NETWORK PASSWORD -- If you're using the networking option, it now has an added level of security requiring a password. (This is useful if an employee leaves and you need to make sure they can't access your Campground Master data remotely.) Usually this password is set to a unique value for your park when you upgrade, and it will work automatically (assuming you remember to install the new version on ALL computers). However if you're having a problem connecting due to an incorrect password, simply go into Network Setup and enter a new password on the Master and also each client computer. Once they all match, the connection will be successful.

SECURE OPERATOR PASSWORDS -- More secure passwords, automatic log-outs, and password expirations are now supported. These features are disabled by default for most operator logins to avoid undue annoyances, so you need to go into Park Setup / Operators to modify each operator that you want to make more secure. Also note that current passwords can no longer be viewed, even by an administrator -- so if an operator cannot remember their password then the only option is for the administrator to change it to a new password. (The operator can then privately change it to a different password that cannot be seen by the administrator.)

Also note that the default "Administrator" login can no longer have the password of "Password". If this condition exists, then you will be asked to change the password the next time you log in with that name. See the documentation for more details: help/operatorsetup.html

AUDIT TRAIL -- We've added a detailed Audit Trail of changes made to records and accesses to credit card information. This also tracks records deleted, receipts printed, E-mails sent, operator log in/out activity, cash drawer openings, and more. See here for documentation: help/overview45.html

JOURNAL ENTRIES -- This is a new feature for operator-entered notes. Each reservation, customer, site, vendor, and POS inventory item has its own Journal, plus there's a main system journal. See here for documentation: help/overview44.html

NETWORK SYNC ALERTS (disabled by default in version 6.1) -- You can enable this option through Maintenance / Network Functions / Network Setup / Diagnostics. Once enabled, if a synchronization problem is detected, an Alert will be shown with the recommendation to request a full database refresh. We suspect that you will see these pretty quickly and possibly often. We do recommend doing the full database refresh on each client to resolve the problems, however please let us know if you keep getting the alerts on the same workstation to the point that it becomes annoying. See here for Alerts documentation: help/overview42.html

Important notes on the Net Sync alerts:

• You should expect to see a number of these alerts appear soon after upgrading (due to pre-existing issues).
• Be sure to click "Dismiss" on the alerts to keep the same alert from re-appearing later. Just clicking "Close" will keep them in the queue.
• Perform the recommended action on one of the alerts (if several appear with the same action recommended, then you don't need to repeat it for each one).
• After requesting a database refresh from each client computer and dismissing any existing alerts, they may be seen occasionally as new sync issues arise. Repeat the recommended action whenever possible. This is not considered a "problem" unless it happens several times per day.