Let me explain why I ask:

In my development copy of the mdb, I built the application
with the Tools, Startup, Advanced, Use Access Special Keys
setting checked - pretty much from the very beginning.

When I compile any user's mde file, I use the same source mdb
file to feed the mde creation process. Afterward, I do nothing to
the mde, as a rule. From installation to installation, the
applications differ only in minor content of certain tables, label
control content on the main menu form and maybe some other
very minor differences. Most definitely, I've never monkeyed
with the setting of the above decribed menuitems.

Finished installations in the runtime environment seem to vary in
their behavior. Some allow the F-11 keystroke to open the dbase
window - others do not.

I've wondered if its due to versioning. Perhaps I did something
different in preparing the original installation fileset at some
sites. I can't recall. Each time I do a new revision rollout and a
data migration, I find myself crossing my fingers hoping that the
behavior will change from site to site. Apparently it is not going to.
Maybe this setting is to the runtime executable itself and not data-
base file-specific. Sound right?

Anyway... The F-11 key is quite handy, actually. But if I'm unable
to improve the reliability of its use in my runtime rollouts, I'll use
the following work-around in code...

        DoCmd.SelectObject acTable, "tblAdmin", True

The line has always worked for me.