Combo box on form

[Kryst51]

One thing with your posted, db, set up your relationship in the relationship screen, this is necessary.

Relationships should look like this attachment when you are done

 

[Kryst51]

Alright, one mistake I made was having to do with that query. You do want the record source to be just the table, so instead of clicking onthe box with the three dots, you want it to just be the tbltABLE from the drop down menu.

 

[Kryst51]

Seriously read up on normalization, I think you could have a lot of issues going on here.

--but my reason for this particular post is to tell you that you need to make your data types in your tables more definitive. Your field "date" allows text to be entered, you should set an input mask. Also you shouldn't name it "date" Date is a reserved word in Access, so maybe call it "OrderDate" or something like that.

 

[Kryst51]

Alright! Bob Larson is very much to thanks for making this work. (My ideas that seem simple when I start, never turn out that way once I get going, So I too, then need help) But try this on for size!

 

[rob.lyles]

Hey, thanks both you and Bob for working on this. It looks great! THANKS

Rob

 

[rob.lyles]

On the same order number, can an order number be on more than one record in the main table?

Ok, I made a mistake in my speaking here. Yes, the order number can be on more than one record as multiple items on that order are entered into the form. So the order number field and part number fields would come together to be unique. Is this easy to implement?

 

[Kryst51]

Ok, I made a mistake in my speaking here. Yes, the order number can be on more than one record as multiple items on that order are entered into the form. So the order number field and part number fields would come together to be unique. Is this easy to implement?

Ok, you definetly have a normalization issues here.

Please read up on normalization, I don't think you should go any further until you solve these issues.

Is the db you posted shortened? maybe post your full db minus the actual data as well as a description of what you want to accomplish (the purpose of the db) if this was not a complete version. Someone here might be able to make suggestions. But, don't assume that we will do all the work. Read up on normalization, this site has some great threads on the subject. If you have any questions about what you read please feel free to ask. it's better to take time to learn at the beginning so you are not kicking yourself for bad design later.

Edit: look a post 12 in this thread for a link to a thread that contains a good explanation on how to learn normalization from the doc man.