ContributionsMost RecentMost LikesSolutionsUsing a non-key field for a lookup? And/or Choosing a single record from a table based on other criteria...?So this may or may not even be possible but I'm trying to see if anyone else has experience with anything similar. Essentially I'm trying to setup a table that will find the oldest record within a table, based on a common field between the two tables(non-key), and then pull that oldest item's key field over into another table. I know this cannot be done directly between the two main tables since I'm not directly referencing the key field of the parent table, so I tried creating another in-between table that will show any related items that have that common non-key field. This is doable, but I have no way of then pulling the oldest key field into another table from there, the best I can do is take a look at all the related items that show up in the report, sort by the date, and get the key field value manually from there. Does anyone have any ideas on how this might be achieved?Re: Using the ""last modified by"" field as a reference field?The way I have it set up they should only be editing that record once in a day (each individual user anyway, as the edit process moves along other users will also edit). I'll definitely setup the trigger the way you suggested only when the last modified field changes so we're only recording one "event" record for that person for a particular record. I think that should also help keep them from purposefully padding their numbers. This method should provide me with lots of other opportunities as well, such as error tracking and things like that. Absolutely fantastic.Re: Using the ""last modified by"" field as a reference field?Wow. I cannot believe I didn't think of that. Thanks again for the help guys!Re: Using the ""last modified by"" field as a reference field?Basically I need to track the last modified field to see how many records are being edited by that person in a day (obviously this wouldn't track if the last modified was already this user, but I would also use the date to exclude this). The way that I have the data separated basically I'll be tracking those fields for different lengths of time. 1 day, weekly, monthly, etc. It's going to be used as a performance monitor as they're supposed to be editing a certain amount of records per day. The actual data that they're editing is unimportant, it's just how many records they're editing for now. Essentially it would be complete record change monitoring on a per user basis. Obviously the way that I'll track each one will be set up a little differently depending on their role/interaction, I just want all of their performance data in one place and captured in an automated way.Re: Using the ""last modified by"" field as a reference field?Mark, your solution worked perfectly. I had tried your idea previously, but I set the field to a Formula Text field like an idiot. After changing the type to Formula User it is now working properly. Matthew, I tested what you are suggesting, but I am unable to change the field type of the [Related Resource] to formula - user without breaking the previously established relationship and having it output the last modification to my user table itself. I also cannot change the [last modified by] field's type in the related table. I am interested in your solution as it seems a bit cleaner. I'm going to have to connect a lot of different tables to this one user table to monitor records/performance of users using summary fields, so not having to create mirror fields would be preferable. Would you be willing to elaborate a bit on your explanation of your solution? I assume I'm probably editing the wrong field or misunderstood what you said.Using the ""last modified by"" field as a reference field?I'm trying to create a user table as discussed in this other post: https://community.quickbase.com/quickbase/topics/weekly-user-activity-report. However, it seems that I am unable to set the reference field to [Last Modified By] when creating a relationship between my users table and the table I'm referencing. I'm not sure why, as both fields are "user" fields. I realize the post I'm referencing is old, so maybe they've changed the functionality. Is there another way to approach this problem perhaps? I've searched around and couldn't find anything on this topic, but maybe it's something dumb that I'm overlooking.