In my application I currently connect to three different Access databases via the Table Adapter, Dataset and databinding source....
The software will ship with 2006 data......when 2007 comes around is there a way to post an updated database to my website and have the program merge the newer data with the older data
Let's say for argument that the 2006 database has 1200 records and they added another 12 themselves. Then when 2007 comes around I would like to be able to let them somehow click get 2007 data and have the 2006 local database go out and grab JUST the 2007 data and not overwrite the whole database....
Possible Can someone point in the right direction....I have searched for keyword 'merge' that turned up little...... Is there a keyword that I can do a search with

How would I update a whole ACCESS database???
Art102
I get that quite a bit: I use VB2005Express - it does have a cut down version of the MDSN library/help, as stated in the descriptive comparison of the Visual Studio versions.
In that case, you will have to go to the MSDN (MSDN2) online library.
(hmmm, another reason to upgrade, perhaps )
TMacPhail
mesh
Thanks for the ideas and replies but I was hoping for either a tutorial or an example of how someone else has done it with a little nudge of code....
Is it just me or is the documentation for VS2005 REALLY BAD It seems like no matter what I search for I get something like this:
The index entry you selected has no target topics associated with it.
To view topics related to the index entry
Click one of the child items listed below the index entry.
See Also
Then you click a subitem and get even less!!!!!
The documentation needs some work......
Assimalyst
mangelp
What version of VB do you have
Thomas Lee
CamCC
You can probably do this through SQL commands, provided that you know all the tables that need to be updated. Is there anything other than data that needs to be updated Table structures QueryDefs Reports
RFewing
There an alternative architecture that could be adopted that will take care of your sychronization problems.
You can always write a server that handles the I/O. When it does all the I/O itself, the server can queue the I/O requests and there woun't be any synching problems.
patel_mitesh
Assuming I'm understanding you're question. Here's what I would do:
In your application include an update function and a way for the appropriate user to start it. The function would open a recordset to the new data and process each row.
For each row it would check the old database and if it finds a matching row update the appropriate fields. If it does not find a matching row add a new row to the existing DB.
If your application is in Access I would do it the same way by creating a subroutine in a module and creating a form to call the subroutine with the appropriate data.
Grasssu
Here's the structure.....
One table in the 2006 Database that has 1200 records with 8 columns of specs....
One Query that simply creates a single record for each MFG.....that is driven by the table and I have verified adding records to the table automatically updates the query....
When the 2007 MFG specs come out I dont want to make a whole new database to dispurse....I would like to be able to keep a master DB on the web with ALL specs and when they connect it will ask them if they want to synchronize the local data with the online data and have a local up to date database......
I have searched a bit for synchronization......merge and DB updates and I really cant find much that pettains to this. I KNOW it must be possible because there are a bazillion softwares that sync local to web data and visa versa....
Thanks in advance for the solution......