Multiple Operations for a Job Order

[FlabbyRoach]

That is exactly what I mean


If the user inputs a customer that is not on the list, can that customer be added, but not duplicated?

[aytee111]

Yes it can be added. The event you need is the NotInList event. When a user enters a customer that does not exist this event will be fired off and you add the customer to the table.

[FlabbyRoach]

That will work for me.
Is it in the properties of the text box?

[orange]

I looked at aytee111's comments and revisions. I suggest you create a model of the things in your business at a high/logical level, and get the relationships set to meet your business rules/facts. Your can test your model to ensure it meets your requirements and revise as necessary until it does.
Then, you can build the database based on the underlying model. If you don't want to include the Customer or some other entity, you don't have to focus on that, but you know where it fits in the model. And when you decide to include that entity, there is no guessing; you just work from the model.

Here is a jpg representing the "new" tables proposed by aytee111.

[FlabbyRoach]

Thank You
I will work on that model and see what I can come up with.

[FlabbyRoach]

orange,
here is the new tables for my project.

[FlabbyRoach]

And here is the DB so far.
I still need to tweak it a bit.
ProcessSheets.zip