Using old 3.13/4.03 databases (data, log, photos) in 5.x Software

[Runway 31]

John,

Myflights are the flights your box is picking up.

Alan

[John Racars]

Thank you verry much Alan!

I understand all about MyFlight now but I saw not what was happening when pressing the button or F9..........

It is clear to me now.

[Netcop]

It's nice to hear that the next release of the software will check the existing photo folder first and use the photos from there automatically as all we believe. It will give me a possibility for smooth migration of my huge current photobase into v5 version.

Below is my idea how current users may obtain a possibility for smooth migration of their aircraft database from current their Navdata base to V5 version. Personally, I have a lot of manually changed records in this base and in many cases even don't remember if this record was manually updated.  But I want to keep my changes untouched during Auto-Populate procedure in v5 (other than changing Autoupdate field to N for hundreds and hundreds records). And also I want to keep working Auto-Populate function in my v5 system.

All that  I ask AirNav to do to protect my own previous work on database -  is implement one more choice button in the Preferences/RadarBox/Photo and Aircraft Auto-Populate area - Do not overwrite existing aircrafts records.



If this button will be ticked, the Auto-Populate procedure will be process in the "old" V3.13/4.03 way:

AutoPopulate function just adds a new entry to a database if this aircraft is new (entry with specific Mode-S address does not exist in database). If entry with specific Mode-S address already exists, AutoPopulate doesn't attempt to overwrite current entry with server one, basically didn't do anything in this case.

I don't think that implementation of my idea will need a lot of programming efforts from AirNav side but will definitely provide a lot of benefits for current RadarBox users.

Regards,
Nick

[Runway 31]

Only problem that I can see is where changes are made to the details other than the hexcode for example when the code is re-allocated to another aircraft or when the operator changes.  Another example here in the UK the hex code stays with the aircraft with registration changes.

Alan

[vonsmalhausen]

I just did a update of the DB ( aircraft only ) with the auto-populate aircraft data ticked.
at first sight none of the records that I have changed with the auto-update set to N so far in the DB seems to have changed after this, so I assume the photo I assigned in the PTTN field will be loaded.
so, is it ok to leave the auto-populate on to get new records, without having you're photos changed, as long as you set auto-update to N ?........ sorry to be a pain, but I just do not understand this new way of how the DB works.

[Netcop]

Hi Alan,

Yes, I see both of yours points. But my idea here is to find some solution which would give RаdarBox’s veterans a simple way to migrate their own databases to v5 and to keep them working. Radarbox’s  veterans are aware about limitations which you have highlighted, I believe.

This a possible button (I mean - Do not overwrite existing aircrafts records) isn’t a rule but just a choice. AirNav has established a lot of strict rules in V5, I believe that AirNav may give us a choice as well...

Regards,
Nick

[Runway 31]

I understand what you mean Nick and your suggestion has been forwarded and is being considered.

Alan

[Netcop]

Thanks, Alan

Nick

[Runway 31]

vomsmalhausen, When updating the whole database you must also set the Sync Option to Do Not Update Manually Changed Records,

I would suggest that you try it with the photos of a couple of aircraft that you see every day to ensure that you have it correct.

Alan

[vonsmalhausen]

Alan, the Sync option for manually changed records is set to "do not update"
for the moment, I spend my free time to alter my DB to "N" for auto update, ad a timestamp and a filename in PTTN, and also delete the regular LK/LK1 and PT/PT2 fields for the records I have a recent/correct picture.
this work will take me several more weeks, meanwhile, I simply don't have the time to check if updates alter my work back to scratch (for the moment I do not connect my box anymore, just launch the program to work with the DB explorer ).
maybe if I get to the "OO-" part of the DB, i'll be able to spend a couple of days checking out some settings, but this lies WEEKS ahead of me.
meanwhile, thanks for the tips and suggests so far ( and I second Netcops suggestion for the "Do not overwrite existing aircrafts records" option )

[Runway 31]

I think I would check first

Alan