Is it possible to Password Protect a Form?

  • Thread starter Thread starter Tim
  • Start date Start date
T

Tim

By this I mean that if a users is going to a screen that
adds a record or something, is there a way to ask for a
password to allow access (and thus add a record) to that
users, or tell them no if they have not got one?

TIA
Tim
 
Does your application require some type of login? Based on the login, do you
assign some type of rights, such as 'User', 'Admin', 'User-ReadOnly',
'User-ReadWrite', etc.

Keep a table that tracks what form the user (or the rights of the user) can
open or not open.

For example, if all users can open Form1 and within Form1 there exists a
command button that opens Form2, you would check in the table (i.e.
tblRights) to see if the user can open Form2. If not, then you can disable
the command button.

Basically, you will have a table of all the forms the user (or user rights)
can and cannot access. When it comes to opening those forms, you can do a
lookup against the table to see if the form can be opened.

--
Rob

FMS Professional Solutions Group
http://www.fmsinc.com/consulting

Software Tools for .NET, SQL Server, Visual Basic & Access
http://www.fmsinc.com

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 
Rob

Thanks for that, a good kick off point. As it is
(although the requirement may come later on) there is no
such login required at this stage. If it is, I'll follow
the route you have suggeested.
For now, only 1 person is allowed access to a certina
bit - I was figuring giving them the password and letting
them update as needed.

Cheers
tim
-----Original Message-----
Does your application require some type of login? Based on the login, do you
assign some type of rights, such
Click to expand...
as 'User', 'Admin', 'User-ReadOnly',
 
You could always build code to ask for a password. It is not real secure
though (if you release the file as an MDE then they can't get into the VBA
and see your password). I think you can also password protect your vba
code.

In either case, they may be able to get around this by opening the table
directly.

By using user security as mentioned by Rob, you can handle it better. I
would not build a table though, I would simply go into the built in security
and set user or group permissions. For the user who can add data, give him
"insert data" priveledges in the table. For the rest, don't.


Rick


Rob

Thanks for that, a good kick off point. As it is
(although the requirement may come later on) there is no
such login required at this stage. If it is, I'll follow
the route you have suggeested.
For now, only 1 person is allowed access to a certina
bit - I was figuring giving them the password and letting
them update as needed.

Cheers
tim
-----Original Message-----
Does your application require some type of login? Based on the login, do you
assign some type of rights, such
Click to expand...
as 'User', 'Admin', 'User-ReadOnly',
 
Back
Top