3 Replies Latest reply on Aug 10, 2010 2:01 PM by philmodjunk

    Layout Visit Tracking Log


      Layout Visit Tracking Log


      Is there a way to track the layouts a user goes to when using the database? Having acquired a database in which I think numerous layouts are not even used anymore, I would like to track which layouts are being used and which ones are not. Ideally it would be a log file that would list the User Name and each layout visited during their session. I currently have a table that tracks login name/time and logoff time. Not sure if I should tie into that for this purpose.

       I am using V.8

      Any ideas would be appreciated!


        • 1. Re: Layout Visit Tracking Log

          Since version 8 doesn't have script triggers, you'd have to limit layout navigation strictly to scripts performed by clicking buttons or by selecting them from the scripts menu.

          If that can be set up, just include steps in each such script that logs the user (or account) name and layout name in the log table.

          Something like this can be put in a single script and then called by every script that changes layouts:

          Freeze Window
          Set Variable [$LayoutName; Value: Get ( LayoutName ) ]
          Go To Layout [LayoutLogger]
          New Record/Request
          Set Field [ LayoutLog::UserName ; Get ( UserName ) ] //or use get (account name)
          Go To Layout [Original Layout]

          The challenge here, is that you'd also need to go through every single script that might have the go to layout or Go To Related Records script steps and insert a call to this script in every case where you find those script steps.

          • 2. Re: Layout Visit Tracking Log

            Thanks Phil! You confirmed some of my thoughts and got me past my mental block for the next step in moving forward. I'm pretty sure the script steps you listed will do the trick!

            • 3. Re: Layout Visit Tracking Log

              Don't know what you can still get for v8, but with filemaker 10 and 11, you can use filemaker advanced to generate a database design report that can help you analyze what parts of an older system might not be needed anymore. There are also third party applications that take the DDR and provide enhanced analyses that would likely be very useful for this.

              I put my old converted from 5.5 tables on a "field diet"--deleting dozens of no longer used fields by doing systematic text searches of each field name in the DDR. If I couldn't find it anywhere but in the field definition, it was a good candidate for removal.