That's why I asked, because it should NOT be that way. "Everyone" needs to learn how to use a database and we're attempting to help you out here. Keeping quotes and active jobs separated is NOT an appropriate way to handle this. As ghudson mentioned, you mark them active or not. You do not give users access to the tables so they should never need worry about what goes on under the covers. You can provide them QUERIES with Forms to give them what they need.
Does that make sense?
So, anyway, I was asking as I'm looking trying to understand what we need to keep and what we don't. Job Description would be what I would use and will use in my example, if they are the same thing.
I completely understand what your saying. I am going to redesign the database in the long run because I want to run it on sql instead anyways. So I am going to keep these two table merged into one and use queries to seperate.
Though I am still left with how to track jobs individually. You see, if every job has 20 purchase orders, I need to track that in a new table with columns and rows... so not sure what to do here.