Maybe I'm misunderstanding...

Here's my view of the data in your combined db:

ID Location blah, blah, blah

1 East
2 East
3 East
2 North
3 North
1 West
2 West
4 West
1 South
2 South
3 South
4 South
99 South

Notice that you can have multiple identical IDs (but also note that these
CAN NOT be autonumber type in the combined table!), distinguishable by their
Locations.

To do this, I would leave the Locations/sites doing their thing with their
own Autonumbers, then use a query to append the records into my "master"
table. When I appended the records, I'd be putting the ID numbers into a
new Numeric/LongInt field (that's the counterpart/equivalent of what
Autonumber generates).

Again, DO NOT attempt to append autonumbers (from Locations) into an
autonumber (in main table) field ... and Access won't let you duplicate an
already used Autonumber, so this might be moot!

Good luck!


Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

"Rlong via AccessMonster.com" u58125@uwe wrote in message
news:a6ef7556ec99c@uwe...
Thanks, Jeff. Yes, I am using 2007. I'm not sure what the "replication"
feature was, but it sounds like it isn't an option anyway for 2007.

So, regarding the combination field--I'm unclear how this would work, as I
didn't think you could create a "calculated field" in a table. And,
assuming
I did do this, would I need to do this for all the primary key/foreign key
combinations manually throughout the database? As you can tell, I'm on the
newer end of the continuum when it comes to database construction, and
have
little coding experience--most of what I've done is menu-driven.

Thanks

Jeff Boyce wrote:
I didn't notice which version of Access you are using. This is important
because the Replication feature went away for the ?2007 version. If
you're
up to it, that might be a way if you're using the earlier (pre- 2007)
versions.

An alternate approach might be to add in a single field that holds the
location. The combination of your autonumber PLUS the
location/facility/site/... will give you a way to identify which records
belong to which site.

Now, if you were trying to use Access Autonumbers as sequence numbers,
you're in for a bit of pain. Access Autonumbers are intended to uniquely
identify rows. That's it! Not guaranteed sequential, can/will have
missing
values.

Good luck!

Regards

Jeff Boyce
Microsoft Access MVP

I've created a small but somewhat complex relational database that uses
autonumber fields in higher level tables as primary keys to link with
[quoted text clipped - 22 lines]

Thanks

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...esign/201004/1