Greetings,

Suppose I have a database with a category for Region, and the
possibilities are North, South, East, and West. (I might want to add
regions in the future, and some tables will have more than one record
per region, so Region needs to be its own column rather than having
columns for North, South, East, and West individually.)

Now let's say that there are some tables that use Region, where I want
to allow only one record for North, one record for South, one for
East, and one for West.

What is the best way to accomplish this?

Thanks,
Rachel

Put all the data in one table and make Region the primary key of that table.

Peter
http://access.xps350.com/

In the table in which you want only one record per region, index the Region
column, and, in the properties, specify "no duplicates".

As XPS350 said, if you make Region a Primary Key, it will be indexed with no
duplicates allowed, but it is not _necessary_ that Region be the Primary
Key, only with properties as I described.

--
Larry Linson, Microsoft Office Access MVP
Co-author: "Microsoft Access Small Business Solutions", published by Wiley
Access newsgroup support is alive and well in USENET
comp.databases.ms-access


"Rachel Garrett" <(E-Mail Removed)> wrote in message
news:1ade8bf2-4746-44e4-924f-(E-Mail Removed)...
> Greetings,
>
> Suppose I have a database with a category for Region, and the
> possibilities are North, South, East, and West. (I might want to add
> regions in the future, and some tables will have more than one record
> per region, so Region needs to be its own column rather than having
> columns for North, South, East, and West individually.)
>
> Now let's say that there are some tables that use Region, where I want
> to allow only one record for North, one record for South, one for
> East, and one for West.
>
> What is the best way to accomplish this?
>
> Thanks,
> Rachel

On Aug 12, 1:51*pm, "Access Developer" <accde...@gmail.com> wrote:
> In the table in which you want only one record per region, index the Region
> column, and, in the properties, specify "no duplicates".
>
> As XPS350 said, if you make Region a Primary Key, it will be indexed withno
> duplicates allowed, but it is not _necessary_ that Region be the Primary
> Key, only with properties as I described.

Thanks; I'll use this.

--Rachel