I have a database that contains 9 s 1

[rlh777]

I have a database that contains 9 subforms. The main form is called, "Customer Information". This form is linked to the tbl_Customer. Two of the columns in this table are Customer ID and Customer Name. When I open the "Customer Information" form and select a customer, certain information defaults throughout the form. I would like certain information to default to my 9 subforms as well. All subforms have a field called "Customer Name". I would like to be able to open the Cusotomer Information form, select the customer, and when the information defaults, I would like to take it a step further and have the customer name go to each subform. Right now the customer id is the only thing that goes. Any thoughts? HELP!

 

[CJTyo]

So, for the three that do not put the info in the table what is different about that field on those forms from the six that DO? Check in design view. What are the Control Sources for that field on those three forms versus one of the ones (not the main) that works okay?

As for the Indeterminate, it's most likely because the same field is unique across all tables.

Try checking the forms as mentioned in my first paragraph because the second paragraph one is bringing me back to your original table/db design and you seemed pretty sure you didn't want to rethink that at this point.

C *~*~*~*~*~*~*~*~*~*~*~*~*
Insanity is a matter of Perception.

 

[sonso]

Most people don't understand the relational database theory; you need to understand the difference between a primary key and a foreign key. Each database product implements this differently. The customer table should have a primary key of just CustomerID (yes, you could make it autoNumber, but conceptually it's the same thing). More importantly is the link to the "child" (detail) tables. When you have an autonumber as the primary key there, you could have duplicate records allowed. E.g. a customer should be able to order a particular item only once per order. Thus the item # would be *part* of the primary key. You would add CustomerID+Part# to get a unique identifier for the order (leaving out the order number or line number...you get the idea). As CJTyo said, you need to read the first few chapters of your documentation to understand the relationships between your tables.

 

[rlh777]

Okay..I got my tables to have a one-to-many relationship. That's good. I'm looking for the differences in the forms now. I am definitely open to changing the original design, the only problem is that the majority of information is copied from another database.

 

[JeremyNYC]

For a great discussion of the fundamentals of relational database design, check out the developers section on my website (below). There's an article written by Paul Litwin that will teach you an immense amount.

Jeremy =============
Jeremy Wallace
Designing, Developing, and Deploying Access Databases Since 1995

http://www.AlphaBetCityDataworks.com

Take a look at the Developer's section of the site for some helpful fundamentals.


Remember to reward helpful posts with the stars they deserve.

 

[CJTyo]

Well, in this case hopefully we can make it work for you. You'll want to review normalization, relationships, and basic relational DB design theory before making your own from scratch. Actually, the review would probably be good for you anyway because it sounds like you'll be redesigning this puppy sooner rather than later regardless. ;-)

C *~*~*~*~*~*~*~*~*~*~*~*~*
Insanity is a matter of Perception.