Database Structure

[SASHA_D]

Hi Everyone,

I have a question about database design. I have been a 'user' of access for a couple of years-designing queries, reports, forms etc.
However, this has usually been on existing databases, never had to design a large or complicated database from scratch-until now!
The basis for the database are a number of tables that come from external sources and are imported to the database each month. The database will only be used for viewing data, no data input or editing is required by the user-apart from on one field in one table which the user would like to be able to change.
I have designed search forms, reports and so on and a form for updating the one field. This all seems to work nicely, but the question I have is that I have used lots of different queries to 'run' the database-I havn't tounched the relationships tab and defined any joins between tables. Do I need to this? or because the database is in the main used for only viewing data is it OK?
Am I likely to run into problems further down the road?


Thanks in advance,

Sasha

 

[ColinEssex]

Hi Sasha -

Have all (or some) of the tables got a common thread? like an ID number or are they all "unjoinable"

Col

 

[SASHA_D]

Hi Col,

Thanks for the reply.
Not all tables have a common thread.......
Around 7 of the tables have a 'product ID' field. 5 of these are joined together using an SQL Union query.
There is then a large table which does not have the said 'Product ID' field-on this table I am running a query that combines 3 fields together. This combined field is linked to another table-'Actual Products' where I have also created the combined field.
The 'Actual products' table contains the 'product ID' field which is then used to link to the tables/query I first mentioned.
Further to this I then have a 'Usage' table-this does not contain the 'product ID' or the combination of 3 fields. Instead it has another ID which is linked to a further table (called 'England'). The England table contains the 'product ID' which again is linked to the Union query and other tables.
Phew!-Is this making any sense??