I was wondering if you can do a calculation and after the calculation is performed it stays unique to that DB.

Example:

I have an employee database which has a "hourly rate" field.

I also have a timesheet DB that looks at the employee "hourly rate" and calculates the hours work times the rate.

If months later I want to increase the hourly rate I do not want it to affect any previous timesheets, just the new records.

Any help is appreciated:

Dave

A couple of solutions come to mind.

The simplest is to create a related file that contains employee names and hourly rates. Then, have the "hourly rate" field in the main database perform a lookup. That way, the hourly rate for each individual timesheet will be whatever it was at that time, unaffected by changes in that employee's rate.

I'm sorry - I do not see how that will keep the field the same - what will keep all the previous timesheets from changing when I change the employee hourly rate?

The "hourly rate" field in the timesheet DB is not a calc field, but a number field with the lookup.