Software Release Download Page
|
| Build | Version | Download | Release Notes | E-mail* | RSS Feed | Manuals | Index/PDF |
|---|---|---|---|---|---|---|---|
| DataSplice 4.0 | 4.0.267.0 |
|
|
|
 DS-4.0 Index |
||
| DataSplice 3.1 | 3.1.388.0 |
|
|
|
DS-3.1 Index |
||
| MAXIMO Plug-in 4.1 | 4.1.241.0 |
|
|
|
Maximo Plug-in.pdf - 2.68 MB |
||
| Printer Plug-in 2.3 | 2.3.22 |
|
|
|
Barcode Printer Plug-in.pdf - 780 KB |
||
| Printer Plug-in 2.2 | 2.2.32 |
|
|
|
Barcode Printer Plug-in.pdf - 780 KB |
||
| CampMaster 1.0 | 1.0.46 |
|
Release Notes |
|
CampMaster Plug-in.pdf - 780 KB |
*DataSplice 4.0 System Requirements*
- Email - support@datasplice.com
* Phone - 800-377-1974 ext. 1730
Upgrading DataSplice
In general, you can just copy and paste the Clients and Server folders into your current DataSplice 4.0 folder overwriting the previous version. Be careful to re-install all of the components that were originally installed or you could possibly end up with an installation that has multiple versions residing in the same directory.
Client Versions
We strive to keep new versions of DataSplice backwards compatible, so Remote Clients with the previous version will still be able to connect to the Server. However, this is not always possible, and some upgrades will block connections from older releases. If Windmill is being used this is not much of a problem. The Windmill administrator simply needs to be contacted to provide the new release, and the handhelds will automatically detect this and upgrade.
Backing up the Current Installation
It goes without saying that before any upgrade is attempted, a complete backup of the current installation should be made. Simply copying the root installation folder will save all the current application and configuration files. This will ensure that everything can be rolled-back to the old version if needed.
Upgrading Views and Plug-in Modules
View upgrades are much more complicated, especially in the case where the module upgrade provides changes and the local view settings have been modified as well. The best solution to this requires project coordination between everyone writing views to ensure that changes are propagated to the latest versions. If this does not happen, there are many "diff" utilities available to merge the changes from both sets of files.
Microsoft Partner Silver Independent Software Vendor (ISV)
This site conforms to the following standards:
