The "easier way" i would recommend would be to not use a repeating field for this. Instead, you would set up a related table. One approach might be to set up a table where you add one record for each working day for each employee--related by an Employee Id number to the original table of employees. You'd log the hours worked, hours out sick, on vacation... etc in this table and use calculaitons and summary fields to compute the total hours worked, on vacation, sick, etc to compare against the totals that they are allowed--values you'd store in the original employees table.
Ok. So perhaps a silly question, but how do I set up a related table? Also, not sure if this changes anything but I have version 6 of FileMaker Pro.
There are many, many differences between FileMaker 6 and Filemaker 10 or 11. I strongly recommend you include that info with your question if you return to this forum with new questions in the future. It'll really help make sure the suggestions you get are appropriate for your version of FileMaker.
To create a new table in FileMaker 6, you'd create a new file and then use "Define Relationships" (I think that's what they called it in version 6) to define a relationship linking the two files. (FileMaker 6 was the last version released that limited you to one table for each file.) You may need to read up on how to do this in the help system.
Once you've done that, you can access the data in the related table via a portal or even by adding fields from the related file/table directly to your layout. You can also navigate to the other file and edit data directly on a layout to your new table in that file. Buttons/scripts can be set up for that purpose.
Thank you, PhilModjunk. I did mean to write that I was using version 6 in my original post but in my eagerness to get my problem fixed I forgot. Thank you for the suggestion I will definitely indicate this next time.
I have used the relational databases once before but I am just not sure what I would be putting in it for this database. I want any my original database to always be the one in which information is entered, so what information am I referencing in the other relational database?
See my response to the new thread where you have asked this question.
"I want any my original database to always be the one in which information is entered,"
While you can use a portal to the new file's table for that, it's also possible to use scripts/buttons to switch files and enter data directly into the new file with employee data from the original file displayed on the layout in the new file. In some cases, this can make for a better option than keeping all your data entry actions in the original file.