Customer/Job/Rates Design

[dcavaiani]

System is evolving!

Right now, there is no Job # or job table.

Just a simple customer table tied to a rate table which has an effective and discontinued date for the rates (may be multiple start/end combinations which skip no calendar dates) used to apply toward billings - by work accomplished date lookup.

Thinking of adding a job # table related to each customer.

Now I wonder if rates s/b locked into the job table rather than (OR in addition to) using a dated rate table as before. Not sure if we would need to change rates DURING the duration of a 'long" ongoing job? Some jobs are BID while most are T and M.

Got a great design related answer last time. Wonder what may be suggested for me this time - maybe something I have not yet even considered ?

 

[plog]

From the sounds of it, the rate should still be tied to the Customer.

 

[dcavaiani]

From the sounds of it, the rate should still be tied to the Customer.

Either way, it would be.

 

[plog]

Either way what? You just posted about how you didn't know if it should be tied to the job or remain tied to the customer. My advice was technical, not a casual statement:

Your rate should be tied to the customer.

 

[dcavaiani]

I missed what U said. You meant that the Rate table should NOT be tied to the Job table, right?

 

[plog]

Yes that is correct.