Show names / unnamed wpts / Intersections causes crash

[Adrian Milewski]

Hi Tim,

I've just upgraded my installation to 0.9.1.423 (on win7) and I am having an issue displaying waypoint intersections. Each time I try to add either named or unnamed Wpts from the ribbon to the display PlanG crashes with the message "Plan G has stopped working".

Checking the log file it seems that the intersection waypoints are missing from the database

20:16:01 Exception plotting named intersections: System.Data.OleDb.OleDbException: The Microsoft Jet database engine cannot find the input table or query 'IsecX'.  Make sure it exists and that its name is spelled correctly.
   at System.Data.OleDb.OleDbCommand.ExecuteCommandTextErrorHandling(OleDbHResult hr)
   at System.Data.OleDb.OleDbCommand.ExecuteCommandTextForSingleResult(tagDBPARAMS dbParams, Object& executeResult)
   at System.Data.OleDb.OleDbCommand.ExecuteCommandText(Object& executeResult)
   at System.Data.OleDb.OleDbCommand.ExecuteCommand(CommandBehavior behavior, Object& executeResult)
   at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior behavior, String method)
   at System.Data.OleDb.OleDbCommand.ExecuteReader(CommandBehavior behavior)
   at System.Data.OleDb.OleDbCommand.ExecuteReader()
   at Plan_G.DataAccess.GetWaypointsInBounds(Double n, Double s, Double e, Double w, Boolean isFSX, Boolean isNamed)
   at Plan_G.MapHandler.PlotISEC_Named(Double north, Double south, Double east, Double west)
   at Plan_G.MapHandler.PlotOverlayElements(Double north, Double south, Double east, Double west, Double centreLat, Double centreLng, Single zoom)

And looking at the Database I can't see a table called IsecX which it is looking for. I have rebuilt the database from scratch but still get the error.

Can you point me in the right direction?

Thanks

Adrian.

[tim arnot]

Did you copy your database from the older version? That'd cause the problem. You must use the database included with 423, and rebuild.

[Adrian Milewski]

Thanks Tim - that worked.

I had originally transferred in my old database and then I rebuilt over that database.

Putting the DB that came with the new version and rebuilding over the top of that has now fixed my problem.

Thanks.