3 Replies Latest reply on Oct 31, 2012 6:29 AM by mikebeargie

    Mailing list design


      I am creating a simple application to keep enter names and addresses in. My goal is simply to print envelopes using the names and addresses entered. The problem ( as I see it ) is the name can be both a "addressee" and a "return address".


      Although it may never happen, the situation may arise where the "addressee" and "return address" are the same name and address. Obviously, I want to create a layout for the user to select the addressee and return address from a file. And that brings up the problem, how do I have two different records (addressee and return address) displayed on the same layout? I was originally thinking that I would have a record structure that had fields for the addressee and the return address in the each record, and then when a name and address is entered, it would be duplicated in the return address fields. However, I don't see how I could get the addressee and return address from two different records on one layout.


      How should I approach this?

        • 1. Re: Mailing list design

          Your original thought would be my thought as well. Auto-populate the return address fields from the main fields. What you CAN do is make a button that copies it from the addressee to the return, making it optional to the data entry person. This way they can just manually enter a different return address if it's not the same.


          Pulling return address from different records can become messy once you start getting a lot of records into the system. I'd try to keep it as simple as possible, and correctly train the people doing data entry to use the copy button or manually enter the return address.

          • 2. Re: Mailing list design



            Thanks for the reply.  I'm still thinking that there is a problem with trying to get data from two records in the same table on ONE layout?  Generally, the addressee and return address will be from different records so how would you populate the layout with two different records in the same table?

            • 3. Re: Mailing list design

              Keeping it simple would mean taking the two-record concept out of the equation.


              To do what you suggest, you would have to create a self-join relationship (make an instance/copy of your table, then relate it back to to the main table). Then you would have to create a process where from a record in the first table instance, you "join" a record from the second table instance (which is in fact the same table) to that record. You would then display data from this self-joined table as your return address. It would also technically allow you to join a record to itself.


              The joining part can be handled by either a 2-part value list, or by creating a multi-stage script that allows the user to go to another list view and choose the record to "join", processing what you need via scripts and variables. You could also make a button that just joins a record to itself, rather than choosing a join record.