How to change relationships?

[adham]

Hey there,

I was wondering if it was possible that anyone could please help me.

I have two tables, one is the main table (GeneralInformation) with two
ID fields, a websiteID (primary key) and a supplierID. In the second
table (SupplierInformation) i have one ID field, supplierID, which is
the primary key. The format of the database is that each website can
have many suppliers, so a 1 to many relationship, but it only seems to
work the other way round.

Can someone please help me out with this?

Regards
Adham

[spier]

On May 29, 3:00 pm, adham <[e-mail]:

Hey there,

I was wondering if it was possible that anyone could please help me.

I have two tables, one is the main table (GeneralInformation) with two
ID fields, a websiteID (primary key) and a supplierID. In the second
table (SupplierInformation) i have one ID field, supplierID, which is
the primary key. The format of the database is that each website can
have many suppliers, so a 1 to many relationship, but it only seems to
work the other way round.

Can someone please help me out with this?

Regards
Adham

In relational design, the basic rule is: children knows their parent.
Thus, SupplierInformation should have a websiteID foreign key, meaning
that the current supplier participate in the website referenced by
websiteID column.

Now, if a supplier may participate in more websites, an extra table
relating websites with suppliers should be created, e.g.
WebsiteSuppliers( websiteID, supplierID), setting both columns as the
primary key.

As you may have realized, MS-Access is far easier than English ;)

[adham]

On May 29, 11:27 am, spier <[e-mail]:

On May 29, 3:00 pm, adham <[e-mail]:

Hey there,

I was wondering if it was possible that anyone could please help me.

I have two tables, one is the main table (GeneralInformation) with two
ID fields, a websiteID (primary key) and a supplierID. In the second
table (SupplierInformation) i have one ID field, supplierID, which is
the primary key. The format of the database is that each website can
have many suppliers, so a 1 to many relationship, but it only seems to
work the other way round.

Can someone please help me out with this?

Regards
Adham

In relational design, the basic rule is: children knows their parent.
Thus, SupplierInformation should have a websiteID foreign key, meaning
that the current supplier participate in the website referenced by
websiteID column.

Now, if a supplier may participate in more websites, an extra table
relating websites with suppliers should be created, e.g.
WebsiteSuppliers( websiteID, supplierID), setting both columns as the
primary key.

As you may have realized, MS-Access is far easier than English ;)

Yes it is unfortunatly.

Ok let me rephrase, why the F*&% does access pick its own
relationships (1 to 1 or 1 to many etc), and is there a way that i can
decide that (which relationship should exist between tables), seeing
that i am the person creating the database.

Thanks
Adham

[adham]

On May 29, 12:06 pm, adham <[e-mail]:

On May 29, 11:27 am, spier <[e-mail]:

On May 29, 3:00 pm, adham <[e-mail]:

Hey there,

I was wondering if it was possible that anyone could please help me.

I have two tables, one is the main table (GeneralInformation) with two
ID fields, a websiteID (primary key) and a supplierID. In the second
table (SupplierInformation) i have one ID field, supplierID, which is
the primary key. The format of the database is that each website can
have many suppliers, so a 1 to many relationship, but it only seems to
work the other way round.

Can someone please help me out with this?

Regards
Adham

In relational design, the basic rule is: children knows their parent.
Thus, SupplierInformation should have a websiteID foreign key, meaning
that the current supplier participate in the website referenced by
websiteID column.

Now, if a supplier may participate in more websites, an extra table
relating websites with suppliers should be created, e.g.
WebsiteSuppliers( websiteID, supplierID), setting both columns as the
primary key.

As you may have realized, MS-Access is far easier than English ;)

Yes it is unfortunatly.

Ok let me rephrase, why the F*&% does access pick its own
relationships (1 to 1 or 1 to many etc), and is there a way that i can
decide that (which relationship should exist between tables), seeing
that i am the person creating the database.

Thanks
Adham- Hide quoted text -

- Show quoted text -

Thats alright, i just figured it out. You have to specify the correct
indexing conditions. im such an idiot.

thanks for helping out.

regrads
adham

[spier]

>

As you may have realized, MS-Access is far easier than English ;)

Yes it is unfortunatly.

Well, as a foreign, I was telling about my english ...

>
Ok let me rephrase, why the F*&% does access pick its own
relationships (1 to 1 or 1 to many etc), and is there a way that i can
decide that (which relationship should exist between tables), seeing
that i am the person creating the database.

Every time one draw a relation between two primary keys ( and, maybe,
autonumber columns), he/she will get a 1 to 1 relation. Toi create a
foreign key, you have to select a long numeric data type.

[adham]

On May 29, 12:35 pm, spier <[e-mail]:

As you may have realized, MS-Access is far easier than English ;)

Yes it is unfortunatly.

Well, as a foreign, I was telling about my english ...

Ok let me rephrase, why the F*&% does access pick its own
relationships (1 to 1 or 1 to many etc), and is there a way that i can
decide that (which relationship should exist between tables), seeing
that i am the person creating the database.

Every time one draw a relation between two primary keys ( and, maybe,
autonumber columns), he/she will get a 1 to 1 relation. Toi create a
foreign key, you have to select a long numeric data type.

I didnt notice anything about your english. Where are you from
originally?

Just wondering, could you please explain the difference between a
foreign key and a primary key?

Regards
Adham

[adham]

On May 29, 12:35 pm, spier <[e-mail]:

As you may have realized, MS-Access is far easier than English ;)

Yes it is unfortunatly.

Well, as a foreign, I was telling about my english ...

Ok let me rephrase, why the F*&% does access pick its own
relationships (1 to 1 or 1 to many etc), and is there a way that i can
decide that (which relationship should exist between tables), seeing
that i am the person creating the database.

Every time one draw a relation between two primary keys ( and, maybe,
autonumber columns), he/she will get a 1 to 1 relation. Toi create a
foreign key, you have to select a long numeric data type.

I didnt notice anything about your english. Where are you from
originally?

Just wondering, could you please explain the difference between a
foreign key and a primary key?

Regards
Adham

[spier]

>

As you may have realized, MS-Access is far easier than English ;)

Yes it is unfortunatly.

Well, as a foreign, I was telling about my english ...

>
Ok let me rephrase, why the F*&% does access pick its own
relationships (1 to 1 or 1 to many etc), and is there a way that i can
decide that (which relationship should exist between tables), seeing
that i am the person creating the database.

Every time one draw a relation between two primary keys ( and, maybe,
autonumber columns), he/she will get a 1 to 1 relation. Toi create a
foreign key, you have to select a long numeric data type.