Kevin, you're very welcome to your opinion, and no offence taken.

MS has had a couple of goes at plugging the FileOpen dialog into Access. The
earlier example was a "common control", but it was quite buggy, and broke
the database when you moved versions, so most of us gave up on it recently.
The more recent example is the FileDialog object supplied by the Office
library, but it is also unworkable. It is version dependent, fails to work
with SaveAs (even though it appears to offer this option), and does not work
at all in the runtime version. So, the API call is still the best approach.

For me, this kind of thing is just mildly annoying. Once you get the API
call working the first time, you just copy the module and use it in any
database where you need this. What really annoys me are the cases where
Access actually *appears* to work but gives you the wrong answers! Those are
the ones I would like to get Microsoft to fix, but I've not been very
successful to date. We are talking about basic stuff like Access sorting
wrongly, returning the wrong records in a query, silently losing the data
you typed into a form, corrupting your data, displaying the wrong
information and so on. Since I can't get them to fix this stuff, the best I
can to is to warn other users about these flaws:
   http://allenbrowne.com/tips.html#flaws

On the positive side, though, MS should be commended for the knowledgebase
where you can get to know about these flaws, traps, and other issues. It is
also commendable that they encourage these groups with free feedback and
assistance, even though we sometimes use these forums to complain about what
we don't like.