3 Replies Latest reply on Mar 27, 2013 7:18 AM by philmodjunk

    Comparing one field across two different tables (layouts)

    MartinReid

      Title

      Comparing one field across two different tables (layouts)

      Post

           Hi, 

           Was wondering if anyone knew a way to comparing or even search across to two different layouts to find if data has been entered twice?

           A bit of background, i have two layouts that contain information, but the second table is amde up from information from the first. the problem is I have many people accessing this one file and updating it and if one unobvlivious user enters the information back into the first table then when end up with duplicates, which doesnt help is the database is up to 50,000 records.

           Thanks
           Martin

        • 1. Re: Comparing one field across two different tables (layouts)
          philmodjunk

               In your database, does this mean that there is only one record in table 2 for every record in table 1?

               If not, please give an example of what you want to prevent.

               There are a number of approaches that can be used.

          • 2. Re: Comparing one field across two different tables (layouts)
            MartinReid

                 its an e-mail campaign db, it has a huge list of current subscribers and a list of unsubscribers. What I am wanting to do is, compare the unsubribers against the list of current subscribers to see if any have been entered into both so i can remove one.

                 They are set out so that one layout has the unsubs and the other has all the current ones so that it is easier to manage.

                  

            • 3. Re: Comparing one field across two different tables (layouts)
              philmodjunk

                   IF you define a relationship linking the two tables by email address, Only email addresses that occur in both tables will show a matching record in the related table. From the Suscribed layout Unsubscribed::emailaddress will not be empty if there is a matching entry in Unsubscribed. From the Unsubscribed layout, the same would be true for SubScribed::EmailAddress.

                   IF you put subscribed and unsubscribed contacts in the same table with a field to identify each, you can use a unique values validation field option to keep this from happening in the first place.