Got some VBA code behind a button.

User clicks a "Save" button, VBA code pushes contents of a
worksheet into an MS Access DB.

The catch is that there are many users - each with their own .XLS
and there's a requirement that one user cannot peek at another
user's info. i.e. Open up the MS Access DB directly and browse
the table we're pushing data into.

I didn't want to get into the MS Access security model, so that
means that the MS Access DB is password protected.

Right now, the PW is in a Const string in the VBA, which feeds it
to a DAO.OpenDatabase via the Connect string.


Seems like a chicken-egg dilemma, but it would be nice if the
code behind that "Save" button could get to the PW, but somehow a
sophisticated user bent on snooping could not.

Only thing I can think of is somehow making it impossible for a
regular user of the .XLS to see VBA code, step through VBA code,
and/or get to an Immediate window.

Suggestions?
--
PeteCresswell