Create a group that contains a single user (and hope nothing ever happens to
that person). Create group permissions in the backend file giving full
permissions to that group. If the database is secured properly (I assume
you mean user-level security, the term by which it is most commonly known)
it will not be possible to open that file by double-clicking on it unless
you are joined to the security workgroup. Rather than changing the default
workgroup to the security workgroup, create a shortcut that opens Access and
joins the user to the security workgroup file for that Access session.
After ending the session the user will be joined to the default workgroup.
The shortcut is something like this:
"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" /user "gaetan"
/wrkgrp "\\ServerName\FolderName\SecureDB.mdw"
The first part is the full path to the Access executable file on the
computer. The user switch is optional, but may make it easier since the
username will be filled in at the password prompt. The wrkgrp switch is the
path to the security mdw file. The security mdw file idenitfies the user,
and the permissions are stored in the Access file. If you are teh user, the
mdw file identifes gaetan and passes that information to Access. Access has
the information that gaetan is a member of the Developer group, and that the
Developer group has full permissions. The shortcut opens the Access
program, but no files. The user uses File > Open to navigate to the Access
file and open it. This will bring the login prompt.
All of this assumes the backend is a mdb file.
The puzzling thing about what you are asking is that the database window and
the back end are entirely different things. You can use the Startup options
to allow or disallow the use of special keys such as F11 to display the
database window. If you disallow their use it is still possible to use the
Shift bypass key to bypass the startup options. The bypass key can be
enabled/disabled programatically. A Google groups search for "Access Shift
Bypass" (without the quotes) should turn up plenty of information. The
database window can be shown or not programatically. I can point you to the
Help topic: StartupShowDBWindow property
However, it involves creating a property, which I have not done, so I have
no further information about that.
To what end do you wish to allow a single user to see the database window,
if that is what you are asking?