Issue:  ShipTo database for Clients, to be accessed during Sales Order record creation, with the chosen ShipTo record being imported into the ShipTo field on the Order form:

Question: Should the ShipTo database be a subform to Clients database (my initial inclination), or should it be a standalone database?

Thanks, Bob.   That was my first inclination, but wanted to see if wiser, bigger brains agreed, or had a different 'take' on it.

I have a field in my customer.db that designates if the cust has multiple shipto adds, so my plan is the Order can check that field and then popup a shipto list or not, depending on the criteria met.

I'm getting close to having my application rounded out and test-ready.  On the development laptop, the capabilities demonstrated are awesome (realtime updating of pricing records when an ItemCost changes, realtime Pricing updating within Order form, create a new inventory record on the fly within the Order form and have it then create a pricing record for that customer .....)  If Sesame performs well/bulletproof in a networked environment I'll be very happy for the 250 hours I'll have spent putting it in place.   
      After running inhouse backoffice stuff and polishing, I'll build the remote order piece for clients to come in and place their own orders on my server (if they wish).  Lordie, what a time saver that will be vs maintaining static HTML weborder pages for some of my clients.

I appreciate your time.