Cak said:
This is the first time I used this board and I was very
impressed with the quick and informative response that
I received. I knew just enough to know that I was in
trouble and should have removed the copy I made but
I was interrupted and then left it to be used.
In the part that I asked about how can I tell where the
data is different, you said "provided there aren't
identification conflicts between the records." I'm not
sure what you meant by this statement. Thanks again for
your help!
Many tables are designed so that the records have a unique identification
field that is of the AutoNumber type (an AutoNumber is normally a Long
Integer that automatically increments between records -- but you can't count
on it being truly sequential because there are circumstances in which a
number or series of numbers may be skipped; in another form, the AutoNumber
can be specified as a replication ID or a Globally Unique ID -- GUID, but
you don't want to 'go there').
If the records added to the separate databases have an AutoNumber type
unique identifier field, your work will be complicated because both users
AutoNumber would have begun where the original database records stopped, and
you will have _duplicates_ of the same key, but identifying different
records. As these are the fields that are usually used to provide the join
between related tables, that can quickly get complicated.
If you can determine where that original database's records stopped, add an
additional field identifying the group to the main table and all related
tables in the original and the separat copies, make it part of the key of
the main table, set it with the identity of the person / group which
initiated the new records (e.g., maybe something as simple "E" for "Eastern
Division" and "W" for "Western Division" -- it will only be for the purpose
of disambiguating references to the records) then copy the original records,
and then append the records from each group to that, you may be able to do
this without quite as much work.
If, as is good practice, you made a backup copy and saved it in your
archives when you made two copies of the DB, then that would let you easily
determine where the copies' autonumbers began.
Look at the main table in design view, look for the field that identifies
the record, look at its type, to see if they are AutoNumber. Then you'll
need to determine the related tables -- those may be evident if you look at
the Relationships, but one doesn't HAVE to define relationships in Access
and some developers do not -- they just use the tables in Queries with
Joins.
Or, if the unique identification of the records is not AutoNumber, but a
number entered by the user, you may just be able to link and do a merge with
APPEND Queries.
In any case, whoever analyzes and tries to restructure/reorganize the
database has to understand what data is there, how it is stored, and work
very carefully (on a copy, repeat, ON A COPY) to try to remedy the
situation. If you begin it this probject on your own as a novice, you won't
likely remain in that status, not unless you run 'screaming into the night'.
Larry Linson
Microsoft Access MVP