Search results

That's what I thought, but I figured it was worth asking since I'm new to this. Thanks for the help!!

I'm looking for general recommendations for handling pay rate increases for employees. That is, the simplest way to structure my DB, would be to include a pay rate in the same table with my employee's other information. But if I do that, and I change that employee's pay rate, then any historical...

99% of the time billing rates are fixed. But we have the oddball case here and there that I'd like to be able to deal with as well. Small projects we do at cost. That sort of thing. I'm not sure we'd charge what the traffic would bear even if we could - maybe that's why we have to keep working...

There are three types of Rates (the last being a fixed rate). You are correct, Emp Rates is not necessary. I think that was a copy/paste error on my part. The intent is to have a Pay Rate and a Billing Rate for each employee.

Attached is a screenshot of an example. The data is just a spreadsheet with the Week Ending Date, the Last Name, The First Name, Employee Number, Earnings Code (straight time or OT), the Contract Code, and the Hours. There are a few other fields, but they are unrelated to anything we do...

I was afraid you might say this. :) Time and attendance is handled by a third party app, and I'm extremely limited on what I'll be able to do with the output. But you are correct. I will try to sort out my database and then try to solve the data import problem. This is where I think I'm stuck...

After thinking a bit about this, I originally intended to use Emp ID, Contract Code, and WE Date as the keys for the Project Hours table. The reasoning was this table would be used to import data from the timesheet application, and I wanted to be able to ensure that each entry was unique, and...

Wow! I got so hung up on needing a many-to-many relationship that it never occurred to me that there was a different way to structure this. Thanks for the feedback! Let me give those changes a whirl and see if I can sort out how to make all that work.

I am trying to put together a database to track both invoicing and payroll for a small business. Things have gotten a little too complicated for Excel to keep up with easily. I've spent several weeks taking a crash course from Google University, and I think I have the basic tables I need put...