Database 1.6 Rev 1 HotFix 1 - Complete (2014-06-25)

Access database files
Post Reply
DiVe
Posts: 431
Joined: Tue Apr 24, 2007 9:14 am
Company: IAT mbh
Location: IAT Berlin - Germany
Contact:

Database 1.6 Rev 1 HotFix 1 - Complete (2014-06-25)

Post by DiVe »

Please find the updated database release for the 1.6.1.
There have been some changes in the database related to minor problems with the long names in the Possible Channels table (MME_POSSIBLE_CHANNELS):
For the codes ??CHSTLO00QADSY?, ??CHSTLELOQADSY? and CHSTRILOQADSY? we changed the word "Upper" to "Lower" in the English Long name.
Also there has been some english longname entries with a second row in the table by mistake. This has no influence on the RED B generation but could have lead to problems if the backend database is used by another software.

In the FL3-table (MME_FINE_LOCATION_3) some links to the figures has been corrected or updated in the PICTURE_SHORTNAMES column. These links are used in the database frontend to open the related figure in the front end GUI if double clicked.

Due to the minor character of the corrections we decide to keep the version number but change the release data of the backend database.
The old database is 1.6.1 issued 2014-04-11
The new database is 1.6.1 issued 2014-06-25

Within the Archive you will find:
- the front end db (V2.44)
- the back end db (V1.6.1, 2014-06-25)
- all the figures in EMF/WMF format
Attachments
ISO_MME_1_6_1_Complete_HotFix1.zip
(3.58 MiB) Downloaded 810 times
cyberkatze
Posts: 2
Joined: Wed Jan 20, 2016 8:34 am
Company: MESSRING Systembau MSG GmbH
Contact:

Re: Database 1.6 Rev 1 HotFix 1 - Complete (2014-06-25)

Post by cyberkatze »

Hallo!

Table "MME_TRANSDUCER_MAIN_LOCATION" have column "REAMRKS", but must be "REMARKS"?
[code]
========================
= Mobile-/Web-Developer
========================
= Home: http://www.cyberkatze.de
= de.linkedin.com/in/alielderov
========================
[/code]
DiVe
Posts: 431
Joined: Tue Apr 24, 2007 9:14 am
Company: IAT mbh
Location: IAT Berlin - Germany
Contact:

Re: Database 1.6 Rev 1 HotFix 1 - Complete (2014-06-25)

Post by DiVe »

Dear "cyberkatze",
that is right. But I have taken over the service for the database and this spelling error is in the database since the beginning. As there might be internal procedures for reporting linked to this "column name", I have not dared to change it.

For the usage there should be no limitation.

Bye,
Dirk
Post Reply

Return to “Database (1.6.x / 2.x)”