Mike, if you would like to have easy summary totals for each unique combination of Employee and Projects you can make a field on your time card record in the format 1234-Related Project where 1234 is the EE#.
Then set up a new table called Employee Project Time and set the key field to be a text field called EE#-Project.
Then you can make a summary report on Time Cards on that field and use the More button to copy these to another table and initialize that summary table. Make relationships to pull in the project name and the company name. make summary fields to summarize totals up to that Employee Projects table.
Also make a formula check ox field on that Summary table called EE#-Project exists, with a formula value of true and look that up down to the Time cards table. Lookup that field down to the time cards table.
To maintain the table going forward you can use an Automation to fire off the time cards when a record is added or edited and the EE#-Project record does not exists.
Then you can also go back to that initial summary report off the time card table and filter it on the EE#-Project Exists field = unchecked, and subscribe to it. That will give you an easy safety net in case the Automation fails.
As for the record count issue, its' not likely to be an issue until you get over 500,000 records. maybe even 1 million. If the app starts to get to slow, you can always just copy the whole app with data and called it an archive version. Then give you main app a haircut to purge out old time records. But it may end up being more than 500,000 records before you have a problem, so I would not even worry about that now.
Quick Base keeps making incremental improvements to performance especially on high record counts, so that will also be helping you each year avoid a purge.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.commarkshnier2@gmail.com
------------------------------