If you set up user-level security, then the user will type the userid and
password when they open the database. You can then determine who can an
can't use the objects in the database.
In other words, "yes". But not by popping up a prompt when it is run, but
properly implementing password security for the entire database. If you
just pop up a password prompt, what prevents someone from looking at the
actual table?
Rick B
