new aiport country name turns garbage

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Hi simmers,
I want to ask if anyone knows how to correct strange country names as AL, DZ, AP etc when adding a new ICAO code to the ultime traffic database while importing an airline flight package.

Example : 

ICAO code: LTFJ
IATA code : SAW
City : Istanbul 
Airport : Sabiha Gokcen
Country : Turkey

the outcome of the airport title on the pdf time table file becomes 

Istanbul, AZ (SAW)

Country name Turkey appears as AZ, exact the same problems happens with any new airport added while importing an airline flighplan package.

In contrast, for instance, the native Istanbul airport on UT database Istanbul Ataturk - LTBA / IST appears as it should be in the pdf output, ie Istanbul, Turkey (IST)

Thanks in advance.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
kvari Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: February-14-2016 Points: 7	Post Options Post Reply Quote kvari Report Post Thanks(0) Quote Reply Topic: new aiport country name turns garbage Posted: September-01-2016 at 6:50am
	Hi simmers, I want to ask if anyone knows how to correct strange country names as AL, DZ, AP etc when adding a new ICAO code to the ultime traffic database while importing an airline flight package. Example : ICAO code: LTFJ IATA code : SAW City : Istanbul Airport : Sabiha Gokcen Country : Turkey the outcome of the airport title on the pdf time table file becomes Istanbul, AZ (SAW) Country name Turkey appears as AZ, exact the same problems happens with any new airport added while importing an airline flighplan package. In contrast, for instance, the native Istanbul airport on UT database Istanbul Ataturk - LTBA / IST appears as it should be in the pdf output, ie Istanbul, Turkey (IST) Thanks in advance.