C# forms and access database

[buddyr]

Hello,
my questions may be rudimental for someone- but for me who has now been struggling with this for hours without sleep - it is not.
I completed a time sheet C# form and connected it to access database.
uers selected their name and filled in hours and submitted.
It worked fine.
Now I have to change it for management.
one I have to add a report that is either printed out for each user or displayed - and by what I have googled - it looks like printing out is easier - is this true?

second: I need security.
Should I have a login box that user first views and from there - they go to their form- or should I make a login on time sheet and user can then access a form with their report and anything else I may have to create in the future to be secure for them?
I am beginner here and if my logic sounds wrong - then without hitting me on the head can someone point out the more logical way I would go about doing this?
thank you

[tlhintoq]

There are a lot of ways someone could go with this. A couple examples could be

• The 'timeclock' doesn't have any report features, thus no need to log in. The HR staff has separate application that does reports and other privileged features.
• Or everyone uses the same program, but it is just put into various modes: Timeclock, ReportStation, HRstation. Changing modes requires a login

.

• Security could be by login/password.
• Or by a card reader for their company IDs.
• Or the application looks for a security dongle on the USB port for management features.
• Or the IP address of the management PCs.
• Or an encrypted document on a thumbdrive contains a users features, ID number and so on. Now clocking in and out is just a matter of plugging in the drive which keeps staff from covering for each other

Personally I tend to have people login with username/password. That reads permissions in to a 'Privileges class' with boolean features like "EditUsers" , "AllowQuit" , "AlterRecor ds" and so on.

From there menu options like "Make new user" have their 'Enabled' property equal to the boolean feature "EditUsers" .

"MakeNewUserMenuItem.Enabled = EditUsers;

So you know the site and environment... What do they needs? What do they want? What can you implement? What is a good fit?

[buddyr]

thank you - your right the time clock form has no need to log in- so I will only have log in for staff data