day to day staff arrival and departure times

[antonyx]

i am unsure as to whether this can be acheived in a database..

basically this task is almost calendar like.

the company operates 7 days a week.
i have a table of company drivers and each has their own driver ID.

my user would like to store what time each driver comes into work each day and what time each driver leaves. this needs to be quite flexible however because some days certain drivers wont work, but each day..if a driver has a 'come to work' time then they will for sure have a 'leave work' time.

each driver also pays rent to the company once a week. within this calendar like system i would also like to store on what day the driver paid what amount towards their weekly rent.

i can quite imagine how this can be done in a database. but if these kind of applications are common, i would be most grateful for some direction.

thank you.

 

[antonyx]

i can quite imagine

this should be i CANT quite imagine..

 

[antonyx]

one more thing..

i would also need to record during each day what time the driver left and returned from lunch (sometimes our drivers leave for a few hours during lunch time)

i want to store this because if they miss a job while they are on an extended lunch break im gonna roast em.

 

[MajP]

Antonyx,
I would think that this would be easy. If I understand correctly, the users would have access to a computer for logging in and out. Basically using Access as a punch clock. You could easily create a form that the user enters their password, and it then collects the time they entered their password.
Who enters the data? The actual driver or a clerk?

 

[antonyx]

basically my user is the only one who will be accessing the database.. the office is located in a different location to where the drivers arrive for work.

my user would need a calendar like system within the database. he will be notified by phone what time the drivers arrive.. leave and so on, and so each day he will need to record these times for each driver...

 

[MajP]

This sounds pretty basic. You may want to look at some of the templates that come with Access. Choose "create Database using a wizard". There are a couple of Time Scheduling examples. There is also a ton of calendar control examples out on the web. I think lebans.com has some utilities. If you Google "Canlendar Control Access" you will find a lot of examples and code out on the web. Check the FAQs on this site as well.

 

[stix4t2]

Let me suggest two more tables, driver's hours and driver's rent paid. Both would include driverid, hours would also have date, workin, lunchout, lunchin and workout. Rent would have date, amount.

The entry would be up to you. I would use a select driver in the header to select a driver. I would use two sub forms to show recent entries so duplication is limited. One subform for hourly and one subform for rent.

Maybe use a listbox of drivers on the left of the header and rent paid on the right. Add hourly below because it has more columns.

Rent paid could be continuous and show entries maybe within the last 30 or 60 days as a quick reference. You could also calculate rent due and add it to this form.

Hourly would have five columns. Date, work in, lunch out, lunch in and work out. The date field could have 3 buttons set below or above it, week before, day before and day after. Default the value to Data(), today, then the user can use the buttons to navigate to the date. Another idea is put a date field in the header as the default so the user could go to each driver and enter info for that day.

The work in and other time fields could be created the same way using buttons to navigate time, or a pop up.

I would make both subforms list in descending, most recent first. And if you are feeling real ambitious, which of course you are, maybe instead of two subforms with listings, you could create two subforms for just entering and then use listbox's to show recent entries.

One other thing to keep in mind, computers can be fallable, so you want to have a form that can be used if the computer is experiencing down time. Risk assessment is always a good idea.

Just a few thoughts.