It sounds like you're trying to de-normalize your database. I'm guessing your database has one table. And each month there are just a few fields that are updated to report the status.
The "correct" structure of your database should be something like:
tblProjects - one-to-many - tblProjectStatus
Put the project information that doesn't change month-to-month in "tblProjects". Give that table a Primary Key. Link tblProjectStatus to that Primary Key by putting a field in tblProjectStatus to hold the value of the Primary Key. tblProjectStatus will contain multiple (many) dates for one project.
There are simple techniques to copy the data from month-to-month. I'll give you a hint but I don't want to explain it because I think it's the wrong route. Simply build an append query that you run one time each month. You really should not be copying "static" data. That is the biggest clue that your database is not normalized.
You might try using Tools | Analyze | Table to get an idea of how to build a more normalized database. Before you start altering your tables with this wizard you should take a backup of your database.
When you get your data normalized you'll have to modify your current reporting queries. But they should be very easy to modify since you only need to extract one of the status records for your currently month reporting properties. It'll be a little more tricky to report the historical status of each project. But that will come easily enough.
Randall J Weers
Membership Vice President
Pacific NorthWest Access Developers Group