Why You Should Keep DBA Updated
DBA Manufacturing is maintained as a single, current product build.
Unlike software products that maintain multiple supported versions for long periods of time, DBA does not maintain separate legacy versions with ongoing service packs and hotfixes. Fixes, compatibility changes, and product improvements are incorporated into the current build only.
Updating is required to stay current with Windows OS changes
It is not a viable option to remain on an old product build, even if you are satisfied with a particular feature set. We continually make internal fixes and adjustments to remain compatible with Windows OS changes. Older versions will not be fully compatible with workstation client installation, server migration, network security, operating system versions, firewalls, etc.
One Current Build
Our support and software maintenance model is based on customers running the current DBA build.
Staying current gives you access to:
•The latest programming fixes
•Current product features
•Updated documentation
•Speed enhancements
•More effective support
If you remain on an older build, you may continue to encounter issues that have already been corrected in a later update.
Updating regularly also makes it easier for users to adapt to changes as they are introduced instead of having to catch up on several builds at once.
How updates are distributed
The latest program version can always be found in the What's New area in the online support center.
When a new update is released, we typically provide notification to customers that have resolved programming issues in our support ticket system. We often follow this up with a newsletter announcement. After the early adopter phase has concluded, we set a notification to Admin users at launch of DBA that a new update is available.
The build number identifies each product version
Each new version of the product is identified with a build number. A typical build number looks like this:
394.0.1
Build Number Segments
The build number consists of three digital segments:
Segment 1 = Build Number
The first segment identifies the 3-digit build number. Each build is a major release with significant new product features. A build typically requires administrator tasks and includes new educational materials.
Segment 2 = Service Pack Number
The middle segment identifies a single digit service pack number. A service pack is a minor release with product improvements. Service packs typically do not require administrator tasks.
Segment 3 = Hotfix Number
The final segment identifies a single digit hotfix number. A “hotfix” release consists of one of more high priority bug fixes.
You can optionally preview updates using the Training Company
Before going live with a new update, you have the option of previewing and experimenting with the update on your own company data by installing the Training Company option. If you have an existing Training Company installed, you will need to go to Windows > Add/Remove Programs and uninstall our old version and and install the latest.
Product Update Documentation
Release Notes
From wherever you download a product update or service pack, whether it is from within the software or from the online support center, the download file is always accompanied by a release notes document in PDF format.
NOTE: Always review the release notes prior to updating because they may include system administrator instructions.
Resolved Programming Issues
A list of resolved programming issues is made available with each product updates and service pack in the What’s New area of the support center.
System Performance Troubleshooting
The following article may help identify systemwide performance issues.
Systemwide Performance Checklist
