You might want to read an Access book to get the basics down...
You can copy, link, import, export, drag and drop, and who knows what else...
The design of the database doesn't really matter. The first thing you need to figure out if you want to add the data to a table in the other database or if you want to create a new table in the other database. This all depend on what you need to do with the data.
i am having an mdb lets say first.mdb i made two copies of the same
mdb after doing some data manipulation with one i want the the same data to be another mdb . Import / export option doesn't work for me since it will import /export along with objects. My need is only to tranfer data.
What if you put the data in a third database, and call it backend.mdb, then link the two databases to the backend.mdb and you are sharing the data between all your applications. i.e. You update first1.mdb and the data changes are readily available in first2.mdb.
I hope I got your point now. If not, explain again and I (or others) can see if we can help you.
Real situation was we have some mdb in which we are stroring data.
but for some reason we sent some of the MDBs to a client for some code modification. During the period of modification we have entered data into MDBs present with us. But after the modification done the client has sent MDBs back to us, data in this MDBs ( from client) are not up to date, But data in our MDB's (with us)is upto date .
mdbs with client are latest when we talk of code
mdbs with us are latest when we talk of data
now we want to sychronize them and get final mdbs with latest code modifications and data .
but i don't know the number of tables or their names or structure but only thing i can say is both mdb's are of same design i have to do it for many number of mdbs atleast 1000 no's so i want to automate the process , your said procedure works if its for single simple mdb.
mdb's i am talking will have atleast 20 tables