Bernard, I didn't go through that in detail, but the general idea seems on
track other than the choice not to use enforced relations.
Relationships should almost always have enforced referential integrity, and
in most cases the foreign key field should also have its Required property
set to Yes.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Bernard Piette" wrote in message
...
Well that's it I'll go a mix of both natural and autonumber primary keys
according to the best use case scenario for each table.
You will find the following to be my understanding of your recommedations.
Allen you said try it out so here it is. Did I follow correctly ?
C:\Documents and Settings\Administrator\Desktop\RDX 18-12-05 Antoine
December 21, 2005
v2.mdb
Table: tblAddresses Page: 1
Columns
Name Type Size
AddressID Long Integer 4
CountryName Text 50
ProvinceOrStateName Text 50
CityName Long Integer 4
PostalCode Long Integer 4
StreetAddress Text 50
AddressName Text 50
Relationships
tblPostalCodestblAddresses
tblPostalCodes tblAddresses
PostalCodeID PostalCode
Attributes: Not Enforced
RelationshipType: One-To-Many
tblCitiestblAddresses
tblCities tblAddresses
CityID CityName
Attributes: Not Enforced
RelationshipType: One-To-Many
tblProvinceOrStatetblAddresses
tblProvinceOrState tblAddresses
ProvinceOrStateName ProvinceOrStateName
Attributes: Not Enforced
RelationshipType: Indeterminate
tblCountriestblAddresses
tblCountries tblAddresses
CountryName CountryName
Attributes: Not Enforced
RelationshipType: One-To-Many
Table: tblCities Page: 3
Columns
Name Type Size
CountryName Text 50
ProvinceOrStateName Text 50
CityName Text 50
CityID Long Integer 4
Relationships
tblCitiestblLocations
tblCities tblLocations
CityID CityName
Attributes: Not Enforced
RelationshipType: One-To-Many
tblCitiestblBuildings
tblCities tblBuildings
CityID CityName
Attributes: Not Enforced
RelationshipType: One-To-Many
tblCitiestblUnitPromisetoPurchase
tblCities tblUnitPromisetoPurc
CityID SignatureCity
Attributes: Not Enforced
RelationshipType: One-To-Many
tblCitiestblAddresses
tblCities tblAddresses
CityID CityName
Attributes: Not Enforced
RelationshipType: One-To-Many
Table: tblCities Page: 4
tblProvinceOrStatetblCities
tblProvinceOrState tblCities
ProvinceOrStateName ProvinceOrStateName
Attributes: Not Enforced
RelationshipType: Indeterminate
Table: tblCountries Page: 5
Columns
Name Type Size
CountryName Text 50
CountryOfficialName Text 50
CountryAbbrev Text 2
CountryDomainExt Text 3
Relationships
tblCountriestblProvinceOrState
tblCountries tblProvinceOrState
CountryName CountryName
Attributes: Not Enforced
RelationshipType: One-To-Many
tblCountriestblAddresses
tblCountries tblAddresses
CountryName CountryName
Attributes: Not Enforced
RelationshipType: One-To-Many
Table: tblLocations Page: 6
Columns
Name Type Size
LocationID Long Integer 4
LocationName Text 50
CountryName Text 50
ProvinceOrStateName Text 50
CityName Long Integer 4
StreetAddress Text 50
Relationships
tblCitiestblLocations
tblCities tblLocations
CityID CityName
Attributes: Not Enforced
RelationshipType: One-To-Many
Table: tblPostalCodes Page: 7
Columns
Name Type Size
PostalCodeID Long Integer 4
PostalCode Text 8
Relationships
tblPostalCodestblAddresses
tblPostalCodes tblAddresses
PostalCodeID PostalCode
Attributes: Not Enforced
RelationshipType: One-To-Many
Table: tblProvinceOrState Page: 8
Columns
Name Type Size
CountryName Text 50
ProvinceOrStateName Text 50
ProvinceAbbrev Text 3
Relationships
tblCountriestblProvinceOrState
tblCountries tblProvinceOrState
CountryName CountryName
Attributes: Not Enforced
RelationshipType: One-To-Many
tblProvinceOrStatetblAddresses
tblProvinceOrState tblAddresses
ProvinceOrStateName ProvinceOrStateName
Attributes: Not Enforced
RelationshipType: Indeterminate
tblProvinceOrStatetblCities
tblProvinceOrState tblCities
ProvinceOrStateName ProvinceOrStateName
Attributes: Not Enforced
RelationshipType: Indeterminate
Thaks Again,
Bernard Piette