Hi Brian - welcome to FileMaker and the FM Community.
A join table would be a good way to go - call it "locker assignments". This will track every instance of an employees use of a particular locker. The relationship from employees to lockers will be a 1 to many relationship - as only 1 employee can been assigned to a locker at one time. The relationship from the lockers to the locker relationships will be 1 to many - as only 1 locker can have an employee assigned to it at one time.
In locker assignments each record will have the foreign key field for the locker and another foreign key field for the employee. Your dates for when an employee started and ended their assignment to a particular locker will be in this field.
The FileMaker Training Series has helpful instruction and training exercises that can take you through setting up a database similar to this: http://info2.filemaker.com/GLFTS13Basics_FTS-13-Basics-Registration-Page.html
Hope this helps. Chris
It would be nice to generate barcodes for each locker. Then using filemaker go have it so you can walk up to a locker, scan the barcode and find out who's locker it is.. But I guess the same is achieved by just entering the existing locker number. Do you see any advantage to using a barcode system vs numerics ?
IMO, barcodes wouldn't be much advantage here. A barcode scanner is just a really fast typist. I think you'd have to have long, hard to type locker numbers and a huge number of lockers and employees to get any return on the time to set up the barcodes.
Thanks, I'm working on it now... I am trying to get a total years of service number for employees and I thought this would work, but its not...
(Get(CurrentDate) -Dateofhire) /365
Any thoughts ??
Dates are stored as the number of days since 1/1/0001.
(Get(CurrentDate) -Dateofhire) will give you the total days of service.
What you need is essentially their employment "age". See Age from dob and also https://community.filemaker.com/search.jspa?q=calculate+age+from+birth