1 Reply Latest reply on Jan 21, 2012 7:34 AM by DanCornett

    Creating a Log to Track Usage



      Creating a Log to Track Usage


      I'm stuck...and can't find anything similar to my situation. 

      I created a self-service database where students can scan their IDs to retrieve their computer passwords.  I'd like to track who scans and when (CurrentDateTime, student ID, first and last name from StudentLogins).

      I have set-up two tables: one is the user interface (UI) and the other contains the student data (StudentLogins).  Fairly straight-forward - a student would scan their ID and their password would pop up within the UI.

      Any suggestions?


        • 1. Re: Creating a Log to Track Usage

          You will need a third table (consider using it in a separate file for ease of maintenance and security) for the logging of the fields you indicated; if this can be run from multiple locations/systems, you might also want to log some kind of "where" information along with the "when" & "who".

          There are many different ways you can 'trigger' a script to run automatically; see the Filemaker Help with the phrase "script triggers".

          As you think about where in the process of "scan an ID", "lookup value", "display value" that you want to trigger a "log this action" script, you also might want to consider other information for the log, such as 'status' of things such as failed scans (if you get that info), failed lookups (i.e.: invalid ID's), empty returned password field, etc.  Recording that type of information in the "log table" will help you more quickly identify problems (deliberate or unintentional).