I love the possibility to keep an up-to-date database for exceptions to the "standard" callsign rules in DXView but recently I have found a limitation that I find a bit frustrating.
If I, for instance, enter VP8PJ in the callsign box and hit ENTER, the grid box ends up empty.
The distance (13931km) shows, however. Since the grid and geographical coordinates are undefined, clicking the Sun button yields an empty array.
When I open the Config's Override List panel and right-click the VP8PJ entry and chose "Populate override content from entity" I get the message "all override components are already populated".
No grid.
Is there a reason to not populate the grid with the entity's default locator?
+ Yes: DXLab treats the grid square specified in an override as accurate enough to count for awards that involve pursuing grid squares, like VUCC. As Joe W4TV explained, the grid square produced by a DXCC Database lookup does not meet that accuracy criterion.
If I simply select VP8-O from the drop down menu, the grid box is populated.
+ I assume that you're referring to the DXCC prefix selector on DXView's Main window. Using the grid square produced by a DXCC Database lookup is accurate enough for the purpose of displaying a great circle path and computing a beam heading.