This release

- doesn't save DX Atlas settings at DXView termination if DX Atlas isn't running (tnx to Bill W6WRT)

- with "Display info in title bars" disabled, displays DXView's  version info in the Main window's title bar (tnx to John K1ESE)

- if the Settings table in the DXCC database contains unexpected entries, displays a message to the user rather than generate an errorlog.txt entry (tnx to Steve K5FR)

- corrects erroneous longitude tooltip in the GetQTH window (tnx to Tom KQ5S)

- if the USA callsign-to-gridsquare database USAP.mdb is present in DXView's Databases folder, uses this database to determine the location of callsigns in the United States, Hawaii, Alaska, Puerto Rico, US Virgin Islands, Guam, Marianas Islands, and American Samoa

- if a valid QTH latitude and longitude has been specified on the Config window's General tab, makes the current UTC day's sunrise and sunset times available to other DXLab applications

- updates the Configuration.htm, DXCC.htm, and Operation.htm online documentation files


The USAP (for USA and Possessions) database contains a record for each of the ~700K active callsigns issued by the FCC to stations in the USA, Hawaii, Alaska, Puerto Rico, US Virgin Islands, Guam, American Samoa, and the Marianas Islands. Each record contains a callsign, a gridsquare, and a two-character location identifier, which is either a US state abbreviation, PR, VI, GU, AS, or MP. When directed to determine a callsign’s location, DXView uses the DXCC database to determine the callsign's DXCC entity. If the file USAP.mdb was present in DXView's Databases folder at startup and the callsign’s DXCC entity is in the above list, then DXView queries the USAP database. If there's a match, then DXView changes the DXCC entity if necessary, and displays the more accurate location data (region name, CQ zone, ITU zone, local time, lat/lon, and gridsquare) provided by this database. If there's no match, DXView displays location data from the DXCC database. 

The USAP database is constructed by a program that traverses a commercial zipcode-to-location database and two FCC-supplied databases: one that provides a zipcode and unique ID for each FCC-issued callsign, and another that indicates which unique IDs are active (as opposed to expired). The FCC updates its database each month, but I’ll be regenerating and distributing USAP less frequently than that. Archived in a self-extracting executable, USAP is 12 mb in size. Since its both big and optional, I am not including it in either full or development releases of DXView. You can obtain the current version from 

http://www.dxlabsuite.com/dxview/USAP.exe

After downloading, direct the self-extracting executable to place USAP.mdb into DXView's Databases folder.

The current USAP database can always be obtained via the DXView entry in the "Available DXLab Releases" table in

http://www.dxlabsuite.com/download.htm

To determine the date on which your version of USAP was generated, open the General tab DXView's COnfig window and consult the "Database Versions" panel.

If USAP.mdb isn’t present in DXView’s Databases folder at startup, DXView will work just as it did before.


Tnx to Jamie W2QO, Rich W3ZJ, Joe W4TV, and Art W2NRA for their help in testing this release.


DXView 2.9.0 is available via the DXLab Launcher or via http://www.dxlabsuite.com/download.htm .

    73,

        Dave, AA6YQ