Simple three? table setup

[Bernard Piette]

OK, I had to scrap most of my architecture, due to bad table design.

I'm starting with a simple order entry database " the sample from Ms "

Now, I have a products and orders table and all works so I don't want to
reinvent the wheel. But I have a question .

I have only two products for ex: (apples and oranges) but me they are condo
units and parkings. An order can can more than one of each thru the order
details table and all is working. But how do I connect my actual units table
and parkings table to the products table so that every unit and every
parking is a seperate product.
That implies we will have to enter evcery condo as a new product but at
=100,000 a pop it's not like we will enter more than a thousand or so a year
I guess I'm asking how to connect the four tables, Products which are the
Condos and Parkings which are each in their respective tables currently and
the orders table.


Thanks

Bernard Piette

 

[TC]

It's pointless to discuss this until you show us the design of the
tables, including what is the primary key of each table. For example:

tblCustomer
CustID < PK
CustName
etc.

or whatever.

HTH,
TC

 

[Michael Cheng [MSFT]]

Hi Bernard,

As TC said, since table design related questions are very open. Show us the
sample structure of your mdb Access application will help closer to the
resolution.


Sincerely yours,

Michael Cheng
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Tim Ferguson]

That implies we will have to enter evcery condo as a new product but
at =100,000 a pop it's not like we will enter more than a thousand or
so a year

I am not clear what this means. Does each single condo have its own
attributes which need to be recorded?

If yes, then you have no alternative but to record each condo in a record
in a table (or tables). Yes, putting in information about thousands of
things is a significant workload, but it's all part of the business case
you made at start of the project. You did make a bus......?

On the other hand, if they are like tins of beans, then you just record the
fact that there are 12,291 of them with no attempt to track individuals,
just the totals in and out.

Seeing your tables design would be helpful, but in order to understand your
problem, we'd need to hear a lot more about what your database is meant to
achieve.

All the best


Tim F