And you'll be able to use SQL to compare what's in the ARB routes database vs. your own favourite database of routes. For example, I'll be using routes that I've collected using FD6 over the last few months to fill in the gaps in the ARB routes table, using this SQL:
SELECT DISTINCT
RoutesFD6.FlightID,
RoutesFD6.DepICAO,
RoutesFD6.ArrICAO
FROM
RoutesFD6
LEFT OUTER JOIN routes ON (RoutesFD6.FlightID=routes.FN)
WHERE
(routes.FN IS NULL)
ORDER BY
RoutesFD6.FlightID
I'll also be using SQL to look for routes that exist in both ARB and FD6 that have different destination or arrival airports, and reviewing these to see which looks more correct, FD6 or ARB:
SELECT DISTINCT
RoutesFD6.FlightID,
RoutesFD6.DepICAO,
RoutesFD6.ArrICAO,
routes.FN,
routes.NO,
routes.ND,
routes.NV
FROM
RoutesFD6
LEFT OUTER JOIN routes ON (RoutesFD6.FlightID=routes.FN)
WHERE
(RoutesFD6.DepICAO <> routes.NO) OR
(RoutesFD6.ArrICAO <> routes.ND)
ORDER BY
RoutesFD6.FlightID