View Single Post
  #3  
Old April 23rd, 2010, 01:37 AM posted to microsoft.public.access.tablesdbdesign
Rlong via AccessMonster.com
external usenet poster
 
Posts: 7
Default Design for future merging

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