MileMarker 2.0 Revision History


Version 2.00.00 through 2.00.22 (Unreleased)

-- Development:  MileMarker 2 database engine, user interface, and features
                 developed and tested. 

Version 2.00.23 (Released)

-- Release:  This was the initial release of MileMarker 2.

Version 2.00.24 (Released)

-- Fixed:  A potentially dangerous bug that surfaces while
           removing or changing a trip entry. On occasion, the wrong
           trip is removed or changed, resulting in one or more incorrect
           trip entries.

-- Added:  Optional minimizing to tray

Version 2.00.25 (Released)

-- Added:  Option to turn off odometer suggestions

Version 2.00.26 (Released)

-- Added:  Button added to the window that appears the very first time
           MileMarker 2 is used... Button allows importing of old
           MileMarker 1.1 database in one step instead of forcing user
           to create a new database and import the data in two steps...
           Basically, the one button does both of these tasks
           automatically... 

Version 2.00.27 (Released)

-- Added:  Mechanism that prevents multiple instances of
           MileMarker running at the same time.  This is
  	   to prevent possible database corruption.

Version 2.00.28 (Released)

-- Fixed:  Various internal mechanisms optimized. No
           user-related functionality was changed.

Version 2.00.29 (Released)

-- Fixed:  A bug that caused the username of a database to be lost.
	   This resulted in missing usernames on reports and crashes when
           changing database information on licensed versions.
           
Version 2.00.30 (Released)

-- Fixed:  An oversight in design that did not account for users who
           have fraction-of-a-cent reimbursement rates (like $0.275).
           MileMarker now supports tenths-of-a-cent rates.

Version 2.00.31 through 2.00.32 (Unreleased)

-- Fixed:  Various internal enhancements and fixes.

Version 2.00.33 (Released)

-- Fixed:  A bug that added extra "Mileage Data for" text to database
           filename when database information was changed.  This bug caused
           MileMarker to generate a "File Not Found" error after multiple
           database information changes.

Version 2.00.34 through 2.00.37 (Unreleased)

-- Development: Development of trip description enhancements.


Version 2.00.38 (Released)

-- Added:  The ability to include descriptions for each trip. This feature
	   was incorporated in the MileMarker 2 Database Engine (causing the
           DB engine version to change from 2.0 to 2.0a). One extra optional
           argument was added to the DB engine to facilitate the trip
           description data and a new DB engine command ("VERSION") was added
           so that modules that utilize the DB engine can check for proper
           support.  The main MileMarker module was enhanced to support the
           new trip description ability of the DB engine, and the user 
           interface was modified to support the feature.

	   The trip descriptions are stored in a separate file (*.TDD) from
 	   the normal MileMarker databse (*.MM2). This was necessary to speed
	   the development of this feature (incorporating the data into the
           MM2 database file would require a major re-write of the database
           engine).  Full integration of the trip descriptions into the
           MM2 database will likely occur in the next version of MileMarker.

-- Fixed:  A bug that caused the "Minimize To Tray" option to intermittently
           show incorrect status of that option 

-- Enhanced: The calendar control has been enhanced by altering an existing
             function ("Today's date") and by adding a new function ("Show
             today's calendar").

-- Enhanced: A notification message now displays when multiple instances
             of MileMarker are loaded, informing the user that multiple
             instances are not supported.

Version 2.00.39 (Released)

-- Fixed:  A bug that caused the next-to-last trip entered appear on the
           last row of the history box instead of the last trip entered.

Version 2.00.40 (Released)

-- Fixed:  A bug that caused a crash when attempting to create a database on
 	   a write-protected drive.

-- Fixed:  A bug that caused trip descriptions to remain active when a
           a database was erased.

Version 2.00.41 (Released)

-- Fixed:  A bug that caused imported MileMarker 1.1 data to become
           corrupt. This bug was caused by an oversight in the database
           engine 2.0a update (see Version 2.00.38 above).

-- Enhanced:  The database engine now detects situations where database
              information is possibly corrupt. The user is also warned of
              possible problems when database functions are not successful.
              Consequently, the database engine version has changed to 2.1a.

Version 2.00.42 (Unreleased)

-- Fixed:  Various internal fixes and enhancements.

-- Added:  Since the size of a MileMarker2 database is limited (255
           (locations, 32767 trips), MileMarker2 now predicts the remaining
           life of the database (based upon previous usage). This
           information is available in the "Database Information" menu
           option.

Version 2.00.43 (Unreleased)

-- Enhanced:  Various time-consuming tasks now have an indication of
              progress (creating new database, opening database)

Version 2.00.44 (Unreleased)

-- Fixed:  Bug that was introduced in 2.00.43 that caused MileMarker to
           crash when creating a new database.

-- Fixed:  Window repainting problem that caused some areas of MileMarker
           window to become distorted.

Version 2.00.45 (Unreleased)

-- Fixed:  Various internal fixes and enhancements.

Version 2.00.46 (Test Release Only)

-- Added:  Two new commands ("ADJUST AVERAGE DISTANCE" and "RENAME SERIAL
           LOCATION") were added to the MileMarker 2 Database Engine to
           fascilitate altering location information.  Database engine
           version number upgraded to 2.2a.

-- Added:  The ability to change MileMarker's odometer suggestions for
           individual trips.

-- Added:  The ability to rename individual locations. 

-- Enhanced:  Better trip entry/odometer updating.

-- Fixed:  A major bug that caused MileMarker to crash when it could not
           find a database to use.  MileMarker would as for the user's
           choice of action and crash when the user made a selection.

-- Fixed:  A bug that caused MileMarker to remain in memory even after the
           user exited after validating a license.

Version 2.0.47 (Released)

-- Fixed:  Failure to connect to database when importing MileMarker 1.1
           database via the "Can't locate a database" dialog.

-- Fixed:  Incorrect reply message from MileMarker2 database engine when
           "ADD NEW TRIP" command was issued.  Engine was replying
           "OK:CHANGED" when it should have been replying "OK:ADDED". This
           has been fixed.

Version 2.00.48 (Released)

-- Fixed:  Various internal fixes and optimizations.

-- Fixed:  A crash when entering new trip after choosing previous trip in list.

-- Added:  Option to clear the contents of the description box between each trip entry.

-- Enhanced:  Trip descriptions are now printed on a line of their own (this eliminates
              problems with the trip description being too long to print along-side the
              trip information).

Version 2.00.49 (Released)

-- Fixed:  "Type Mismatch" error that occasionally occurred when entering or changing
           trip entries (bug introduced in 2.00.48 description clear option)

-- Added:  Online updating has been added using the RSC Online Update Agent system.


