Splitting a Record between multiple tables

[velcrowe]

I have a purchase order where I tracked how much is ordered for a particular item. I track the order by year. Sometimes however, an order is paid over multiple years. So I have a 240K order that is being paid in 2008 2009 2010. Is there anyway to key the order in my received in 2008 table but show that it will be paid over a 3 year period?

If that isn't possible, is there a way to key an order in one table (say "Orders 2008" and have it populated on the similar table for Order 2009 and Order 2010?

Thank you

 

[speakers_86]

I can try to point you in the right direction, but I dont really understand your needs.

What it sounds like to me is that you need a table for payments made.

Payments Made
PaymentID-PK
Order ID-FK
Date of Payment
Amount

Queries can then be used to to compute accounts payable. Hope that helps.

 

[velcrowe]

Thank you for your help. I am trying to balance my budget for the upcoming year. Certain purchase orders are paid over a few years instead of all at once. When I key an order for the current year, I need to show that although it originated in 2008, the payments will stretch for 2009 2010 2011. So I need to show the order against those budget years as well with the portioned payment. Can I enter the order in 2008 but show the same entry on another table for another budget year. So what I would like to do is duplicate one entry on multiple tables. I hope that helps a little more.

 

[jal]

I have a purchase order where I tracked how much is ordered for a particular item. I track the order by year. Sometimes however, an order is paid over multiple years. So I have a 240K order that is being paid in 2008 2009 2010. Is there anyway to key the order in my received in 2008 table but show that it will be paid over a 3 year period?

If that isn't possible, is there a way to key an order in one table (say "Orders 2008" and have it populated on the similar table for Order 2009 and Order 2010?

Thank you

In my opinion the last poster gave you the right answer. (I'm not an expert, however). However, there is also another issue perhaps worth raising. I doubt it's considered good design to have three tables Orders 2008, Orders 2009, Orders 2010. I should think the preferred design is to have one table called Orders, with a date column called OrderDate or DateOrdered.