Designing Tables

[kaygirl]

I am designing a new database which previously was a flat file table. I have broken this flat file down into four tables but they do not seem to be linking (using queries) very well.

I do not know if I am designing the tables properly. Table 1 is Organisation Information, ie address, etc, Table 2 is Contact, Firstname, Lastname etc Information. The reason for two separate tables is because there could be many contacts for the one organisation - is this correct? or should Contact information and organisation information be in the one table?

 

[SgtJarrow]

If you have (or expect to have) more than one contact per organization, then yes, they should be in separate tables with a one to many relationship from organization to contacts. Programming isn't a profession of choice.
It's a profession of calling...
"Hey Programmer, your application broke again!"

Robert L. Johnson III, A+, Network+, MCP
robert.l.johnson.iii@ssmb.com

 

[Bry12345]

Agree with mstrmage .. the one to many relationship looks fine.

As to the linking not working . . . your 'one' table (Org Info) should have a primary key, a field whose value uniquely identifies that record in the table. For linking, each 'many' table, i.e Contact, etc, should contain a 'foreign key' field whose value is identical to the corresponding row in the 'one' table. Without this key relationship, you won't be able to link properly.

There are some other issues regarding joins in queries, so if these comments don't get it fixed, post again! - - - -

Bry