You're working with Access as you would work with Excel, however an access table is not an Excel sheet. If there are data of the same nature but for different periods of time, they should be stored in the same table, adding rows, not columns to the table. In the case you describe, a column would indicate the concerned period, possibly in a 'yyyymm' format.
So theres no way to make a code that will allow me to insert the data in a column from another table in the same database? other then redesigning the original table and making this into a cross tab query?
Somthing on the lines below? but this is not copying over the data.
CurrentDb.Execute ("UPDATE tbl_Actual_car_Sales SET P201107 = ('tbl_importedData' P201107")
In any case you'll be obliged to issue a DDL SQL statement or use DAO or ADO for modifiying the structure of the table first. This will prevent you from using a relational database the way it is intended to.
The best solution I can come with (except for properly redesigning the database) would consists in creating additional tables (possibly using SELECT ... INTO SQL queries), then linking the different tables with dynamic SELECT queries. But even this does not make a lot of sense.