Didier,Thanks for your help to make things clearer!!<>This gave me the idea to CHEAT:Renamed GEOGRAPH.pod as COUNTRY.pod and......VolEdit could read the Country.dbd database without problem!! :-)To read the other db in the same pod: State.dbd, rename as STATE.pod.There's only one file I can't edit: STATCTRY.dbi which certainly links State and Country databases.I checked the Country.dbd inside my Fly!II/system folder, and it seems to be updated. Certainly that one of my attempts to import the dex worked. However, the changes do not reflect inside Fly! II. We should certainly update STATCTRY.dbi as well.For now, I didn't have any problem opening the navaids from the updated countries. The country just doesn't show. I still have to teleport to a Falkland's airport to see if any problem arises.Thanks for VolView, I never tried to use it before and I'm very impressed! It's an essential tool! And it's fun to play with databases!Pascal :+

STATCTRY is (guessing as per the rest of the indexes) just an index of the sctr field of state database. It shouldnt be linked to the Country.DBD, other than requiring that "US" be identified in Country.DBD. (since the only defined states are in the US.)And... I've come across an error in the Country dex importing. For now DONT bother importing Country.dex.Appearantly (atleast for me) there is a problem somewhere. It doesnt show up until you repod the files. Then I get a crash when attempting to use the flight planner.I'll post back once I know more.Brad

Hello Brad_BI confirm than a friend of mine and me have the same problem attempting to use the flight planner.For Pascal, very nice idea to change the name. All *.DBI files are index and are generated by Fly and DEXimport when importing data.Didier