Form Question

[all7holly]

Hello,
I would like to be able to have an individual form that people could use as there time sheet. This form would need to be separate from everything in my database. I don’t want these employees to access to the rest of my database. Is this possible?

 

[Jeanette Cunningham]

It's possible to restrict their access using a login form that captures the name and password of users.
You would create a table to store the users' name and their password and your login form would verify the user name and password against this table when users login.

Once users have logged in, you need to have code that uses the user name and password info to hide all parts of the database except the time sheet form (depending on the user). You would need to restrict users access to the navigation pane and built in menus, shortcuts and the built-in ribbon.

You can also use the shift key bypass to restrict users opening the database by holding down the shift key and gaining access to the navigation pane that way.

That will restrict 99% of users from accessing the rest of the database. Users who are skilled with access could still gain access to the rest of the database if they really wanted to.

This type of setup is often acceptable - I don't know if that suits you.

 

[all7holly]

Hi Jeanette,

I believe the user name a password would be the way to go. When writing the code to hide all the forms except for the time sheet. Would I need to list each hidden form(there are more than 50)? Would you be so kind to send me all the steps involved in this process?

Thanks,
Holly

 

[Jeanette Cunningham]

The exact steps needed will vary depending on your application.
Do you know how to set the start up options from the File Menu under current database? This is where you set the start up form, hide the navigation pane, restrict the menus and shortcut menus and set the custom ribbon for your app.

 

[missinglinq]

Given your conditions, I don't think I would go with a single database for this! I'd have a separate database for the 'timecard' app, and if you need to access that data from your main database, simply link to the 'timecard' Tables. I really think that this would be far-and-away the simplest solution, rather than spending huge amounts of time trying to bullet-proof your current app.

Linq ;0)>

 

[all7holly]

Wonderful idea! How would I link the timecard form with with the table in my original database?

 

[all7holly]

Also the form is based on a query.