Aviation database for Garmin 2610/2620?

In a previous article, "John Bell" said:
As Paul Tomblin has mentioned, navaid.com will allow you to load aviation
waypoints. You cannot load an entire database. What you can do is load
aviation waypoints as user waypoints.

Paul's site is great. I don't know about the 2610 and 2620, but you can
then load the waypoints from Paul's site with several programs. Some of the
free ones are EasyGPS, www.easygps.com and G7toWin,
http://www.gpsinformation.org/ronh/.

While we're indulging in a little self-promotion here, I'd like to ask
people a question about my waypoint generator. A little while ago I got
frustrated with the fact that the FAA data I get is incredibly
inconsistent about the naming of fixes. It's hard to know what fix types
to ask for, because what I'm usually interested in are fixes on airways,
but the FAA only uses the fix type "AWY-INTXN" about 8 times in the whole
country. Most of the others are called something else, but those
something elses are also used for fixes I have no interest in myself. So
as an experiment, I put a thing in the CoPilot waypoint generator to pick
fixes based on what charts they appear on. So I pick ones that appear on
IFR Enroute Low Altitude charts only, and I'm not troubled by all those
fixes that are only of interest to people with GPSes, or which are part of
Jet Routes, or part of an approach but not in the en-route, etc.

I put that into CoPilot, and asked for feedback. And so far, not a single
person has told me whether they like it or not. So I don't know if I
should bother putting it in the other generators or not, or even if I
put it in INSTEAD of the other fix type picker.

Anybody have any opinions?

--
Paul Tomblin http://xcski.com/blogs/pt/
The language that these files use is just like BASIC, only with all of
the good parts ripped out. Oh, and did I mention that it's case-sensitive?
I could eat a K&R and ****** a better language.