Re: Combining tables from two copies of DB
- From: "[MVP] S.Clark" <steve.clark_NOSPAM@xxxxxxxxxx>
- Date: Mon, 30 Jan 2006 18:09:18 -0500
Although Queries will help in this situation, there probably isn't a single
query that will do it. You will need to determine what got added, when, and
where, and figure out where to put it.
The hardest part is if there are child records when you have to change the
autonumber value.
btw, appending a row to an autonumber table will assign a new number(just
leave the autonumber field out of the query.)
Good luck,
--
Steve Clark, Access MVP
http://www.fmsinc.com/consulting
*FREE* Access Tips: http://www.fmsinc.com/free/tips.html
"BruceM" <bamoob@xxxxxxxxxxxxxxxxxx> wrote in message
news:eeH6cEaJGHA.1312@xxxxxxxxxxxxxxxxxxxxxxx
> Our network person did something pretty incredible when changing computers
> over to a new server. There were some difficulties in the transition, so
> he simply stopped changing over. As a result, for a while people were
> entering data in copies of databases on both the new and old server. I
> will call this time the Period of Confusion. This had been going on for
> at least a week before I discovered that some people weren't seeing
> changes I had made because I made the changes to only one copy of the
> database.
> Two databases seem to have been affected. One is a repair record
> database. The active table (tblRepairRecord) includes the job number, PO
> number, etc. The other table (tblRepairDetails) is for the repair details.
> For instance, there may be a record for Repair Manual 123456, Repair 1;
> and another for Manual 123456, Repair 7. Once one of these records is
> added to tblRepairDetails it doesn't change. tblRepairRecord links to one
> of these static records. No records were added to tblRepairDetails during
> the Period of Confusion. Records were added to the active table. They
> have an autonumber primary key. Now that everybody is once again using
> the same copy of the database, how best to combine the tables?
> The other database is for training records. Each employee participates in
> many training sessions, and each training session may be attended by many
> employees, so there is a many-to-many relationship between Sessions and
> Employees that is resolved through a junction table. If it matters, there
> is no Course table. Training sessions are about the latest revision to a
> work method, and things of that sort. Each record in the Training table
> contains a record of a unique training session. Records were added to the
> Training table in both copies of the database during the Period of
> Confusion. With each such record a listing of employees who attended
> appears in the junction table. Again, I need to combine the tables. I
> mention the database structure in case it has a bearing on how I combine
> tables.
>
.
- Follow-Ups:
- Re: Combining tables from two copies of DB
- From: BruceM
- Re: Combining tables from two copies of DB
- References:
- Combining tables from two copies of DB
- From: BruceM
- Combining tables from two copies of DB
- Prev by Date: Re: How do I combine these queries?
- Next by Date: Re: Show Invoices Greater Than One Year
- Previous by thread: Combining tables from two copies of DB
- Next by thread: Re: Combining tables from two copies of DB
- Index(es):
Relevant Pages
|
