EHM 1 Database Settings Editor

We have come across a seemingly rare bug in the EHM 1 Editor which causes the database to be saved in the incorrect database format. It seems that the Editor switches mid-save from saving in the EHM v1.4.1 format (aka database version 1025) to a tentative EHM v1.5 format (aka database version 1033, albeit this is subject to change). This causes a problem because the ‘Database Version’ setting in the database is set as 1025 whereas the remainder of the database is in fact in version 1033 format. This will cause EHM to crash when trying to create a new game from the database as the game will be trying to process the database using the 1025 format when in fact it is in 1033 format. Similarly, parts of the database will appear to be corrupt when viewing the database in the Editor (notably, the Transfer Rules, Finance Info and Schedule Templates screens will list lots of “Out of Range” entries) – see the screenshot below.

Thankfully there is a simple fix in the event you encounter the issue:

1. Immediately exit the Editor and do not attempt to save the database again. Trying to re-save the corrupted database will cause it be irrecoverable.
2. Download and run the EHM Database Settings Editor.
3. Open the affected database in the EHM Database Settings Editor.
4. The “Created With Version” and “Database Version” settings will most likely be set as 1025. Change both of these to 1033. Then save the database and exit the EHM Database Settings Editor.
5. Re-load the database in the EHM Editor and all should be well again (a good way of checking is that the Transfer Rules screen appears ok).
6. On the Home screen of the Editor, change the Version drop-down menu setting to EHM 1025 and save the database.

The above instructions are on the assumption that the Database Version setting needs to be corrected from 1025 to 1033 to reflect the actual format of the database and then changed back to 1025 for the purposes of EHM v1.4.1. Obviously any future releases of EHM patches will mean that different database version numbers will be relevant.

Whilst I know what is causing the issue, I cannot pinpoint when or why it is actually occurring in the Editor. The EHM Database Settings Editor is intended as a quick fix whilst I try to pinpoint the issue.

Here is an example of the tell-tale sign that there is a version setting mismatch in the database (note all of the “Out of Range” text down the left hand section of the screen):