SARTrack Logo

SARTrack Update history

Debug and Update history of the SARTrack program (Beta Versions):
Main SARTrack Website is at www.sartrack.co.nz
Please join the SARTrack Mailing lists in the SARTrack About box (Under Help)

Version 0.9.784A
27 October 2018

SARTrack (SAR):
- Critical bug fix relating the Team Setup (People Status not clearing)

Version 0.9.784
23 October 2018

SARTrack (SAR & HAM):
- New: Compression system added. All data transfers between Client and Server are now first compressed before transmitted. This makes any download or upload 3 times as fast, and makes a big difference especially with very large Operations.
Also, SARTrack has now a new option (Enabled by default) to only request Updates from the Database Server after a restart.
To make this possible, SARTrack Clients are now saving all databases of a running Operation locally on disk, but EAS-256 encrypted. So these files cannot be read. Only after a successful Login to the Database server, will SARTrack read and decode the files from disk, then request any Updates from the server (based on the last time it disconnected).
This option can be selected in Setup>SAR>Database. If you decide to use the orginal system, where SARTrack requests a full download of the entire Operation after a restart, then the databases will NOT be saved locally. 

- Fix: Objects would not clear properly in the window when an Operation was closed.
- Fix: Log Entry with a Task would not close the Log Entry window and cause a timeout error.
- Fix: Tait Radio connection: Will now be set to 'Pending' (Yellow) after COM port connect, and only show 'Connected' (Green) once valid data has been received.
- Fix: Add Object: Protection against Spaces in the Object Name.
- NEW: Log system: SitRep Log. When a new Log entry is made, a new option 'SitRep' (Situation  Report) can be selected. These will go onto a seperate Timeline. A new 'SitRep' Window can now be opened from the main Log window, which will only show Situation Reports.  It is intended for Managers to write down the current situation. It is NOT intended for Teams in the field during regular Sitreps to show they are still okay...
- New: DTBUsers: There is a new Access Level added: "Monitor" . Database users who have this access level, have read-only access to the entire Operation, but are also allowed to make standard Log entries, and send Messages.  This access level is intended for overview by higher level organisations, who only like to monitor the Operation, and they can use the new SitRep window to only get general status info, without all the details.
- New: Clamped down on logged-in user Access level restrictions. Made sure only people with a high enough access level can perform certain actions.
- New: MAP: Show NZTM (New Zealand) Grid. Select NZTM in Setup>Maps1. Note: It currently NOT possible to show the UTM or NZTM Grid numbers on the Map, only the lines, sorry.
- Fix: Map: Printing: The printing of the Map did not scale right depending on the original size and orientation of the Map. This is now fixed.
- Fix: Map: Show-Hide window: Filter by Date&Time did not include all Object types properly. Some where filtered out while should not have been.
- Fix: Import GPX files: In GPX files with multiple Segments in a single Track, only the first Segment was imported. Now they are appended into a single Track.  Track waypoints who are too close together and waypoints which are outside the selected Date&Time range, will be skipped.
- Change: Edit Object: Copy Coordinates will now only copy the coordinates, without the Tactical name of the Object, to solve the issue the result could not be copied into a single Edit field.
- Fix: People: New person: Would wipe the form when clicking on "Edit Capabilities" before the initial Form was saved.

SARTrack(HAM):
- Fix: Objects owned by own station would timeout because the timestamp was not updated during automatic transmissions.

Database Server (v0.9782):
- New: Compression system added. All data transfers are now first compressed before transmitted. This makes any download or upload 3 times as fast, which makes a big difference especially with very large Operations.   Also, inproved the way the Server synchonizes after a full restart.

Download any additional OSM maps from http://www.sartrack.nl/downloads/examples/ and read the README file on how to install them.
Always read  additional information on the SARTrack two mailing lists (SAR or HAM versions). You can apply from the Help/About box.
SAR and related users, please sign up to the SAR mailing list. Email info@sartrack.co.nz
PLEASE REPORT ANY PROLEMS AND BUGS!


Version 0.9.782
23 August 2018
SARTrack (All)
- Fix: Transmitting APRS Message to a Station via Radio did not work properly because the timer system which allows Message to be send over Radio was no longer working properly. You can only send an APRS Message to a Station by Radio if this station has been heard over the Radio system in the last 60 minutes. This now works again as designed.
- Update: Polish Language file updated.
- Fix: The IFeeds option "InReach" did no longer work because they changed their Server and the SSL protocol. This is now fixed.


Version 0.9.782
10 July 2018
SARTrack (SAR Only)
- Fix: Important: Closing an Active Operation did not work sometimes due to an internal error while clearing the Stations database.

Database Server:
- Fix: in Setup, the "Automatic Startup" would not properly reload after it was set previousely, which would result in it being disabled when the Setup was saved again, without re-checking the entry.
- New: Setup Option to select Automatic Beta Updates. Default is No.


Version 0.9.781F
9 July 2018
SARTrack (SAR Only)
- Fix: Editing People 'Private Database Access' now also can optionally edit the Callsign. This will now be saved, and reloaded on selection of the person.
- Fix: The DTBEdit window now finally works the way it should.
- Fix: Compatibility Update for People-Status updates from the Android App. 


Database Server:
- Fix: Compatibility Update for People-Status updates from the Android App.

Android App Update history here.

Version 0.9.781
25 June 2018
SARTrack (SAR Only)
- New: Prepared SARTrack for use with the new Android App.
- Fix: Team Setup and People Arrival: Corrected the display of the People Status to show the Default Status when the Active Status is Unknown.
- Fix: team Setup: Repaired a non-functional Button to open the Team Status window.
- Small bug fixes.


Database Server:
-
Updated the Server to work with the new Android App.
- Fix: After the Server locked a Login out due to overload, it would not clear properly after 10 minutes.


Version 0.9.780C
9 June 2018
SARTrack (SAR Only)
- Fix: In Team Setup and Team Status you could not select/unselect the visible Team Tabs anymore after the last update.
- Fix: In extreme training situations, the adding of a new Task would unexpectedly be cleared of the screen when other people where saving their Tasks at the same time.
- New: People window: A new window Tab has been added called "Status". In this new window you will shortly be able to edit the Availability of a person into the future; That is, to set the person Available or Unavailable at certain periods (like a holiday). This is part of the new upcoming Android App, where people can do this by themselves as well.
NOTE: The option to do it from SARTrack is not finished yet.
However, you CAN now set the Default Availability status for a person: Either "Available" or "Unknown". This is the status to which the person is reset after an Operation has been closed.

Version 0.9.780B
4 June 2018
SARTrack:
- Fix: Various issues with the Timeout and related display system (which has been rewritten to clean it up)
- New: Missing Person and Operation Periods: When these are created or modified, the full information from the Missing Person and Operation Periods will be added to the Log system, as an 'Automatic Log entry'. This means that these changes will be be available in the Operation Log window, "Reports>Save Complete Operation Logs".
-New: Reports on Clues: You can now Save a detailed report of all Log entries related to Clues. This is available from the Operation Log window, "Reports>Save Clue Logs", and also from the Clues window, "Reports>Save Clue Logs".
-New: Reports on Tasks: You can now Save a detailed report of all Log entries related to Tasks. This is available from the Operation Log window, "Reports>Save Tasks Logs".

All of the above Reports are saved as .TXT files and .CSV files for use in a spreadsheet program.


Version 0.9.780
31 May 2018

SARTrack (SAR Only)
- New: IPP Circle system: Added the "Initial Planning Point" (IPP) to the pulldown list.
- New: IPP Circle system: You can now save an IPP/PLS/LKP when only 300 meter/1000 feet circle is selected.
- Fix: IPP Circle system: Would not allow the LKP to be set from the Missing Person window when the Dispersion Angles where not used.
- Fix: Log Entry and Teams: During a Log Entry, when a NEW Reference (a "Team, Person, etc.") is entered, a *confirmation* is now requested that this Team is in fact to be Created in the Operation. If so, the Team is created, but it will NOT be automatically be added to the Team Setup and Team Status windows. Instead, a 3 second information window will show that a new Team has been created. If a new Team is created via the 'New Team' window in the Team Setup, then this Team will immediately be shown on all Clients's Team Setup and Team Status windows.
- Fix: Log Entry: When Copy-and-Paste text directly into the Log Entry 'Message' box, this would previously be cut of at 80 characters. It is now possible to Paste a large amount of text into the 'Message box'. Also fixed a problem where the text in the 'Message box' would be deleted and revert back to the text in the 'Summary box' when this was edited afterwards.
- Fix: Tasks window: Window did not clear properly after entering a new Task.
- FIX: IMPORTANT: The 'Lock' system used to notify all SARTrack Clients if a record is edited by someone (Missing Person, Operation Period, etc) could cause an uncontrolled loop in some situations where at least two Local Database Servers where connected to a Internet Master Server, and a 'lock' was initiated by a Client. This fix REQUIRES that all SARTrack Servers AND Clients are updated to version 0.9.780, else the 'lock' system will not work.

SARTrack (general)
- New: Messages and Chat windows: It is now possible to re-open a previousely closed Message Chat window, by right-click on a Message in the main Message window, and select 'Open Chat window'.
- Fix: The AGWPE interface did no longer work since I upgraded to a new Compiler. This is now fixed.
- Fix: The Icon "House" was invalid. Now build a new House (Icon).
- Fix: Cleaned up the "Edit Station" window in HAM mode. Removed all SAR related items.
- Fix: Colored Tracks: The random TrackColor generator for Stations did no longer work in HAM mode.
- Fix: Map Labels: Some long standing discrepancies with the Labels not always giving the right Timeout or Last Heard, and not correctly showing the Coordinates and/or Speed & Altitude in some situations.
- New: Import GPS Tracks and Waypoints. You can now set the Date and TIME for the START of the import of GPX files. All Tracks will either be skipped or be cut off at the beginning of the set time, all Waypoints earlier than this time will be skipped. This means it is now possible to remove non-valid parts at the beginning of a Track, by the minute.

Database Server:
- FIX: IMPORTANT: The 'Lock' system used to notify all SARTrack Clients if a record is edited by someone (Missing Person, Operation Period, etc) could cause an uncontrolled loop in some situations where at least two Local Database Servers where connected to a Internet Master Server, and a 'lock' was initiated by a Client. This fix REQUIRES that all SARTrack Clients are also updated to version 0.9.780, else the 'lock' system will not work.
- New: Denial-of-Service protection. The Database will now block any Clients or Local Database Servers which are attempting to connect to often in a short time. The length of the block is currently set to 10 minutes. This feature is mostly designed for Internet based servers.


Manual:
The Manual has been updated to version 0.9.780. In the 'Change Log' you can see which pages you have to replace (you do not have to re-print the entire Manual).

Version 0.9.779A
7 May 2018

SARTrack (SAR Only)
Fix: Team Setup; People List: Due to a single character missing in the SARTrack code (which, by the way, is now at 230,000 lines of source code...), on initial opening of the Team Setup window, the People list was not properly cleared, which resulted in duplicate names in the list. Only happened when the Filter was used (which it is by default, set to the local GroupID).

Version 0.9.779
3 May 2018

SARTrack (SAR Only)
- Fix: Fixed some issues with the drawing and transmitting of Polylines. Also added a warning when users switch from SAR to HAM mode and back, as this overrides some settings.
- Fix: Editing DTB users would refuse to save if the DTBUser was not found in the People database.
- New: The Connection panel for the Database Server will now show Blue when connected, but not yet fully synchronized, and will turn Green when all done.
- Fix: Map window: Fixed inconsistencies when 'Show By Date' was selected. This will now only show the Icon of the Track when this Icon is also within the selected Time range, else it will ONLY show that part of the Track within the Time range, without any Icon. Right-clicking on a Waypoint will show details and owner of the Track.
- Fix: Edit an Object in SAR mode would sometimes cause an internal error.
- Fix: Map windows: Fixed some Icon transparency issues. Some APRS Icons had a transparent background, while it should have been a solid color, which made them difficult to see.
- Change: Map: The 'New Polyline' window now defaults to a line color of Red instead of Black.
- New: Edit Object window (SAR mode): New button 'Copy Coordinates to Clipboard' will do just that. You can then paste the coordinates somewhere else.
- New: 'Keep Radio Trackers on New Operation'. In the Setup>SAR window there is a new setting: 'Keep Radio Trackers'. The default is Checked (enabled). When enabled, when closing an Operation, all active Radio Trackers will be saved.  Then when a New Operation is started, in the Team Setup window>'New Team' you can then directly link a new Team to a previously saved Radio Tracker by ID.
- Update: Updated the Help file.

Also updated the SARTrack Manual to Version 0.9.779. See the 'Changes' page for what has changed.

Database Server:
- Fix: Server did not clear 'Edit Locks' when a Client (which was in Edit mode) would unexpectedly disconnect.
- Updates: Added additional internal features and commands for the upcoming Android App.
- New: The Connection panel for the Internet Master Server will now show Blue when connected, but not yet fully synchronized, and will turn Green when all done.


Also updated the SARTrack Manual to Version 0.9.779. See the 'Changes' page for what has changed.

Database Server:
- Fix: Server did not clear 'Edit Locks' when a Client (which was in Edit mode) would unexpectedly disconnect.
- Updates: Added additional internal features and commands for the upcoming Android App.
- New: The Connection panel for the Internet Master Server will now show Blue when connected, but not yet fully synchronized, and will turn Green when all done.

Version 0.9.778C
6 April 2018

SARTrack (SAR Only)
- Fix: AIS connection panel would stay yellow, while valid AIS data was coming in.
- Fix: People window: A "New Person" could not be edited after saving, until restart.
- Fix: People window: When a NEW Person would be added, it did not save the initial Status properly.
- Fix: TeamSetup: The 'New Team' button would not work immediately after starting a new Operation.
- Fix: TeamSetup: The People list would jump to the top every time when changes where made, while the People Filter was active.
- New: DTB Users window: It is now possible to link a 'DTB User (Database User) to a Person in the People database. This will be a requirement for the upcoming Android App, when SARTrack users can use the App to connect to the Database, and have access to their own personal data. Also, a new 'Lock' option is now visible, but can only be used by SARTrack access level, and will enable the addition of special Database Login's which can not be changed or disabled by normal users (including Supervisor), except when the DTB user Login is owned by the currently logged in user. Also a filter is added to show/hide any automatically added (Private Android App) Login's. 

Database Server:
- Fix: After a NEW installation of a Database Server, after adding a NEW GroupID to the Server, when a New Operation was started, it would not be saved properly and would revert back to 'NONE'.
- New: Server will show Warning on the screen when a SARTrack Client is trying to connect with the *same* Callsign-SSID as the Server itself, on the same computer. (People do this all the time because they do not read the documentation)

Version 0.9.778B
26 March 2018
SARTrack:
- AIS: I have permanently disabled the forwarding of AIS (vessel) data to the APRS system. If you want to share AIS data, you must do this by using a SARTrack Database Server (in SAR mode).

SARTrack (SAR Only)
- Fix: Team Setup window did not always update itself properly after adding/removing People.

Version 0.9.778B Server
17 March 2018
SARTrack Server
- Fix: Fixed several significant Memory leaks.
- Fix: Timeout and disconnect while loading avery large Operation over a slow Internet link. When a large Operation with thousands of Log entries, and hundreds of (GPS Imported) Objects each with thousands of Track Waypoints was loaded, the synchronization between Master Server and Local Server would time out before the data was transfered. Increased the timeout value to 5 minutes, and inserted additional 'ping' signals to try to reset the Timeout system in this situation. This would also affect any SARTrack Client connecting direct to the internet Master server.


Version 0.9.778A
14 March 2018
SARTrack (SAR Only)
- Performance update. When very large databases are transfered, any open windows (Objects, Stations, People, etc) are updated when new data comes in. Improved the system to reduce the screen updates in open windows, so they do not jump to the top of the lists all the time.

Version 0.9.778
12 March 2018

SARTrack (SAR Only)
- Still fixed more issues with the People database, especially the Import/Export system.

Database Server:
- More safety systems added to deal with backwards compatibility of the People database structure.

Version 0.9.777
10 March 2018

SARTrack (All versions):
- Fix: During a new installation of SARTrack, when no Internet is available, program would lock up when trying to send activation email.
- Fix: Incoming AIS position packets will now only be processed once per minute (they come in every few seconds).
- Fix: AIS Vessels (Boats): The option on the Map, when right-clicking on an AIS received vessel, "Get information on..." now works again, with a Website link to MarineTraffic.Com.
- New: Objects window: You can now FILTER Objects by TYPE: Trackers, Polylines, Imported GPX, Permanent and Clues. In addition the manual filter has been changed so that it will search for the text in the Objectname and the Tactical name (and not case sensitive).
- NEW: In all Map windows, in the right-click Popup Menu, a new entry is available called: "LOCAL SHOW / HIDE OPTIONS". This will open a special window in the Map area where you can select a range of Filters to apply to all Stations, Objects and Tracks on the Map. This is a very powerfull feature which will enable you to control in detail what is visible on the local Map. All options in the window are LOCAL only and will not affect other SARTrack computers. The window itself will stay visible on the Map until closed, and it can be moved. Give it a try.

SARTrack (SAR Only)
- Objects: It is now possible to open any attachments to an Object (Images, documents) directly from the Map, the Objects window, and the Object-Edit window, by right-clicking on the Object and select Show Attachments.
- Fix: Edit Stations (in SAR mode): Would not properly save a change to Tactical name or Color.
- Fix: Edit Objects (in SAR mode): Would not properly save a change to Tactical name or Color.
- Fix: Team Setup: Tasks: After changing the Task (or Drag-and-Drop) a Task, but then changing to another Team without first clicking on the Save button, would cause the Task to be marked as assigned, but the Team would not have the Task assigned to it.
Dropping a new Task will now immediately be executed and transmitted. Manually changing a Task will cause a warning to be displayed when trying to switch to another Team without first saving the changes.
It is no longer allowed to drop a single Task into two different Teams. If you want to assign a single Task to two or more Teams, you first have to make copies of it, with different Task ID's.
- New: Operations Log: There is a new option for marking a Log Entry: Mark as "To be Done". For situations where the Log entry is not 'Open', but also not 'Done'.
- Fix: Operations Log: When Marking a Log Entry ('Mark as ...'), the list will no longer jump to the bottom, but will stay where it is.
- New: People Import/Export now has the capability to select the GroupID to Import, or to only Export own GroupID. This *requires* that all People have their GroupID added, so that SARTrack knows to which Group they belong to.
- Fix: When Exporting People, SARTrack will now add a character 'P' in front of the PHONE numbers, to prevent any Spreadsheet program stuffing up the phone numbers (by removing the leading '0' or '+'). During Import this character is removed again.
- Fix: Assignment Type pulldown lists where missing some entries, which caused them to be empty on assignment.
- Change: I decided to completely remove the "Team Info" window, as this was of limited use and tool a lot of resources. The important Team Status window has not been changed.
- Change: I removed the 'Manage Teams' button in Team Setup. Instead, all Team pull-down windows (for example in New Log Entry) will ONLY show Teams which have *People assigned* to them. This means that if you use a system where new Teams are generated every additional day in a large Operation, ONLY Teams which are still active (because they have People in them) will appear in the pull-down lists.  However, in the 'Tab List' of the 'Team Setup' and 'Team Status' ALL Teams are visible, but they can be hidden from the Tabs as required.
- Change: In addition to above, the automatically generated 'Team' entries "Operations" and "General" have been removed. Instead I made room for Team entries "IMT" and "EOC" which will always show up in pull-down lists even if they do not have People assigned to them. But you will have to generate them yourself, as different countries use different names.
- New: Historic Operations: It is now possible to *delete* old Historric Operations from the list. In the Operation Log window, in 'Options>Load Historic Operations', you can now not only select one Operation to load, but also 'check' any Operations you want to delete, and delete these. What this does is delete them from the *list*. The actual Historic Operations will remain on the Server(s) but are basically inaccesible.



Database Server:
- New: Activated the extra TCP port for use with the upcomming Android App.
- Fix: Problem after a 'Connection Refused' from the Master Server, would not reconnect anymore until restarted.
- FIX: Once again I have to fix problems with the People database structure. Due to the fact that I was asked to make the "MemberID" editable, I got in all kinds of problems with the internal People ID which keeps track of the records.
I now had to make yet another change to fix problems with People doubling up, or being overwritten during a People Import because either the MemberID was edited (in different sites) or other changes where made.
It is possible you may have lost some People from your database, of have double entries (with edited MemberID's).
Please check your People database after updating and restarting your Database Servers and SARTrack Clients. Any major problems, please email me.
*** Please make sure you update ALL your Database servers ar the same time to avoid unexpected issues with the People database, and also restart any open SARTrack programs to force a refresh of the database.

Version 0.9.776C
25 January 2018
SARTrack:
- Maps: Unfortunately I had to remove all OpenWeather "Weather Overlay" maps, as the limitations for the 'Key' are so low, nobody could use it anymore. I recommend using the 'OpenPortGuide' Weather overlays.  I also changed the OpenWeather 'Key' for the option "Get Current Weather at Location" on the Map (right-click), which sends a request to the OpenWeather server, and which also did not work anymore due to the same problem.
- Fix: Station Beacons directly send via Database, Timeout and screen updates did not work correctly (Last heard).



Version 0.9.776B
19 December 2017

SARTrack: SAR Only:
- Fix: In the People>Import_People window, the imported People where not transmitted  to the Database Server.

- Database Server 0.9.776C:
- Fix: A problem in the ServerMonitor.exe program causes a lockup when the Monitor is trying to Shutdown the Database Server.  Because of this problem, you may find that doing an Update, both the Monitor program and possible also the Server will lock up.
The best way to Update the Monitor program now, is to try and shutdown the Server from the Monitor (click on the Monitor Icon in the Windows Icon tray, and select "Shutdown Server"). If the Server or Monitor seem to lock up, kill them from the Windows Task Manager (Ctrl-Alt-Del) and after making sure that both are in fact closed, download and install the latest Server package from the website at http://www.sartrack.nz/News.html . This will fix this problem, and on future Updates, the Monitor will be able to properly shutdown, Update and Restart the Database Server.
- Fix: Server and Monitor: They will now respond better to a Windows Shutdown, at which point both will close immediately, instead of sometimes causing a delay in the Windows shutdown procedure.
- Fix: Local Database Server: A problem where during a very bad connection with an Internet Master Server the Local Server would not be able to reconnect, and got into an endless loop. The Local Server will now completely restart after 2 minutes, if it has not received a full Sync from the Internet server in that time.

Version 0.9.775
11 December 2017
SARTrack: SAR Only:
- Fix: In the People Management window, when the list was filtered (searched), a person could not be selected when clicked upon.
- Fix: Closing Operation did not clear People which Status was "Resting" or "Departed".
- Fix: TeamSetup>Print: Did not work after the first time.
- Fix: TeamSetup>Tasks: When selecting a Task by right-click on it, to change its Status, it would not select the the actual Task from the list, except when this was first clicked on with left-click. As a result the wrong Task could be changed.
- New: Objects Window: It is now possible to multi-select Objects, right-click and select 'Hide' or 'Re-Active' for entire groups of Objects at the same time (in SAR mode only). This will make it much easier to hide many objects on the Map when it get overloaded with Icons and/or Tracks.

Database Server:
- Fix: Due to a problem with the previous conversion (to add an internal ID to all People so you can edit the MemberID), duplicate People DTBID's may exist in the People database. This update will correct and repair the People database.
Unfortunately it is possible that some People will lose their current Status (e.g they will be marked as 'Unknown').
*** Please make sure you update ALL your Database servers ar the same time to avoid unexpected issues with the People database, and also restart any open SARTrack programs to force a refresh of the database.
Sorry about this.


Version 0.9.775
28 November 2017
Due to a unavoidable structural change in the People database system, ALL SARTrack Servers and Clients MUST now be updated to the latest version.
The German and New Zealand Internet Database Servers have now been upgraded to Version 0.9.775, and will ONLY accept incoming connections with the SAME Version number.

I have written a technical explanation of the way the SARTrack Client-Server system works. For those who are interested in how it all works, and WHY the Updates are the way they are, please have a read through it:
http://sartrack.nz/ClientServerTechnical.html

SARTrack:
- Local Maps: The way SARTrack deals with 'Local Maps', Image files which are manually installed on a SARTrack Client, has been improved. There is now a new button in the Map window which will open a list of all available Local Maps, and right-clicking on an area where a Local Map is available, will enable you to directly load this Map and bring it to the top.

SARTrack SAR Only:
- People window: It is now possible to change the 'MemberID' of People. This will make it possible to fix any People who where added on-the-fly during an Operation, when their organization's ID was not available. Many other internal changes where made to fix problems with the Availability system, which will be expanded as soon as the upcoming Android App can be used to pre-program when People (Members) are available or unavailable into the future.
- The Database structure for the new 'Comms Plan' is now installed, the actual user interface will follow shortly.
- Database Server: A internal rewrite of the actual TCP Server system has fixed a rare (but critical) problem of the Server going into a 'race condition' which required a server reboot.
Also, an intermittent problem caused by certain network errors, after which a Local Database Server could no longer reconnect to the Internet Master Server, has been fixed.
- Many other small fixes and improvements in the SARTrack Client.



Older Update History 2015-2017
Older Update history 2014