3 Replies Latest reply on Aug 11, 2015 9:12 AM by philmodjunk

    Global Fields or User Records

    oesupport

      Title

      Global Fields or User Records

      Post

      I have a layout built with the sole purpose of displaying data from other tables. I am trying to decide if this table should have 1 record withe Global fields, or if an individual record should be created for each account that logs in to the file.

      Does anyone have experience dealing with both of these methods, and is there any difference in performance between them?

        • 1. Re: Global Fields or User Records
          SteveMartino

          What exactly are you trying to do?  Are you trying to ensure that certain users can only see certain records, or are you trying to keep a log of which users logged into the database and when/how long?

          What do you mean by:

          an individual record should be created for each account that logs in to the file

          an individual record of what?

           

          • 2. Re: Global Fields or User Records
            oesupport

            Ok, so we have Table1, which contains no data. It displays data from other tables via relationships.

            There are 2 ways to hand the records in Table1:

            1.  A single record and all fields are Global

            2.  Multiple records. One for each user. These are usually referred to as User Records.

            • 3. Re: Global Fields or User Records
              philmodjunk

              For purposes of displaying data, either should produce what appears to the user to be identical results. But a set of global match fields for linking to data in related tables seems the simpler solution to set up.

              If the users will edit data on this layout, there might be an advantage to user records--you'd have to test in a multi-user environment and see if it makes any difference in how "edit locking" works.