I need help concerning table issues

[foody]

Hello,

I have a major problem with the tables I have and the forms. This is the scenario: For every single client info (address and so on) it can have many estimates, many invoices and many internal invoices. This applies for all the three what I am going to say next, but I will use the estimate as the info base. For every estimate, it can have only one estimate number, date and attention (estimate-addres) but for every estimate address it can have many orders and for every orders it can have many descriptions. The same concept applies to internal invoices and invoices. For every interninvoice it can have one internal invoice number, date and attention (internal-invoice-address) but for every internal-invoice-address it can have many orders and for every order(s) it can have many descriptions.

Can someone help me do this correctly thanks in advance?

 

[ScottGem]

It sounds like you have several 1-many relations. These are easy to setup. In each table you have a primary key, preferably an autonumber. Wherever a table can have many records that pertain to a single record in another table (i.e. one client having many estimates), you would include the primary key value in the record on the many side as a Foreign key. So the Estimate table would have a ClientID field that would store the ClientID of the related record.

In such a setup the one side is called the parent table and the many side the child table. To enter, edit and view such data you generally use a main/sub form combination where the main form is bound to the parent table and the subform to the child table, linked on the key field.

 

[foody]

Do you have an MSN contact where I can talk with you live? I need to get more clerified with you and I believe live is better than message board. My MSN contact is devastating_battle@hotmail.com

 

[ScottGem]

Actually I'm not sure I agree that live is better in this specific instance. However, while I do have a MSN ID, I'm not available during the day on it. In the interim. Why not take a screenshot of your relationships window and attach that to a post here so we can look at it.

 

[foody]

There you go, I hope that helps. I also posted the important part of the form, to give you the general idea of what I mean by it.

 

[foody]

Here is the other screenshot

 

[ScottGem]

Ok, First, its not recommended to use spaces in Object names. That can come back to haunt you later. Either use mixed case or underscores like:

StoneType or Stone_Type

Second, its a good idea to name your key fields the same in each table. You have ClientID linked to CustomerNumber and InvoiceID to InvoiceDescription. This makes it very difficult to follow your relations.

Third, your screenshot doesn't show everything. You need to expand the table windows so we can see the full names.

I suggest revising and then go from there.

 

[Pat Hartman]

In addition to removing the spaces from the column names, get rid of the special characters also.