Page 1 of 1

Problems with Merge MDB

Posted: Tue Apr 29, 2008 8:07 am
by Peter
When I go to merge multiple databases with the same structure the program seems to the first one and the third database skipping the second database completely even though there is data.

Can you fix this or at least do some checking i.e. query the number of row before import then append and then check that the rows have increased by the same amount.

You can contact me at peterg70 at gmail com (put the dots in)

Posted: Tue Apr 29, 2008 11:32 am
by DigitalVolcano
There is a known problem where if the tables have a primary key, and those primary key values clash in the merge, then the records will be ignored.

A workaround -
Just before hitting the button to start the merge, open up the first access database in the list and remove the primary key on the table. Save and close it. Then start the merge.

The output merged table won't have a primary key (the first database is used as a template), so it will then accept duplicate keys in that column.

Hope this makes sense!
Thanks
DV

Posted: Sat May 03, 2008 4:02 am
by peter
Would like to see a sumary option that shows the database name, number of rows in table, number of rows merged from table.
Will check but no primary key was setup for the databases.
The problem was it was skipping every second database when merging

Posted: Sat May 03, 2008 6:44 am
by Peter
Found the problem No primary key but an Auto Number field that would not accept duplicates was the issue.

Posted: Fri Aug 27, 2010 10:04 am
by Ben
This error occurs when an event has failed to run because Microsoft Office Access cannot evaluate the location of the logic for the event. For example, if the OnOpen property of a form is set to =[Field], this error occurs because Access expects a macro or event name to run when the event is fired.
(How do I resolve this?)

Posted: Fri Aug 27, 2010 2:38 pm
by DV