I have a table or Quotes.  (Name, info, city, state, move in date, move out date, etc)  I have a portal for Apartment Quotes, we send them quotes based on different properties, maybe 3 or 4 options.  Each Apartment Quote has a variety of fields (cost sheet, profit, expenses, etc).  If they decide to take one of the Apartment Quotes, I'd like to easily convert that to a Job.

 

Job has customer (from customer table), property, move in, move out, size, rates, fees, etc.

 

Is there a way to relate them, rather than make a long script and set a hundred variables?  

Not enough info.

 

You can relate anything to anything so that's not an issue.  But you seem to imply that there is an OR choice between relationships or a long script with variables.  That I don't get.

 

To create quotes you'll need a script.  To pick one quote and turn it into a job you'll need a script.  The scripts will use relationships.  So there is not a choice here between one or the other.

 

So let us know where you are stuck specifically and we should be able to help you out.

 

PS: I'm Belgian so I really like the Margritte avatar...

If they have so many fields in common, perhaps Quote and Job should be a single table? Add a "type" or "status" field and in that field have it auto-enter "Quote" by default, and then later you can set it to "Job."

If you want to stick with separate tables, it sounds like a one-to-one relationship, is that right? Each Job corresponds to one and only one Quote, and v. versa? If so, it doesn't really matter whether you store the Job ID in the Quote table or the Quote ID in the Job table. Either one will work.