Time Clock For Employees

[babylon]

Ok Guys, Heres What I Am Looking To Do!

I wrote a database in FM to track all my employees information. Name, Address, Social etc... I have invested in a barcode scan system, and have distributed employee cards out to all of my employees. Now what I want to do is be able to track Time In, Time Outs In The Database. I am figuring I have to make a seperate database for Time In, And For Time Out.... But how do I incorporate it so that I can track the times in and out for all employee.... My employee status is constantly fluctuating, do to the type of business I am in. So number of employees change.... ANY IDEAS?: ANY HELP GREATLY APPRECIATED

[falkaholic]

I'd make an Employee database, a Day database, and a Ins/Out database.

Have a new Day record for every work day. Related the Ins/Outs to that. However you end up tracking employees (bar coded cards,etc), the Ins/Out database tracks which and when employees punched in and out that day.

HTH

[babylon]

Thx Eric......Makes sense, but at the same time I'm still lost. I understand by using the three different databases, but how would I relate the in/outs with all the different employees. That is where I am stumped.

I'm still stuck!! If my question is not in enough detail I will be more then glad to elaborate, obviously..durr Im gettin the help not giving It LOL!!! Any other happily very greatly appreciated......

[LiveOak]

I'm not so sure three files are necessary. I'd probably go with two, Employees and Transactions. Where an transaction is a Employee/Date/Type where Type is In or Out. Several relationships between Employee and Transactions will be useful. One will be just by EmployeeID to give you all transactions for one employee. Other relationships would be based upon compound keys:

EmployeeID/Date/In <--> EmployeeID/Date/Type (Employee file to Trans file)

This could be used to check and see if the employee is In (you can't checkout if you are not "In"). Likewise:

EmployeeID/Date/Out <--> EmployeeID/Date/Type

Points to any Out record for an employee on a given date.

These can be used to check for an In transaction before creating say a matching Out transaction.

-bd

[babylon]

Thx a bunch again guys. I finally figured it out, while playing with it. At the same time I figured out portals, which was confusing me a bit too. Guess U can definetly say I'm a beginner, but My DB is lookin good, and will be ready to ship any day now. Again, thx for getting me on the right track Eric & LiveOak