Are these your relationships?
Computers::ComputerID = ComputerUsers::ComputerID
Users::UserID = ComputerUsers::UserID
Computers_LastUser::ComputerID = ComputerUsers 2::ComputerID (ComputerUsers 2 is sorted by assigned date in descending order.)
Users 2::UserID = ComputerUsers 2::User ID
Try using a one row portal to ComputerUsers 2 and place the name from Users 2 into this portal row and see if that displays the expected name.
Yes, that correctly describes the relationships.
The one row portal idea does work. Users 2::Username is correct in the one row portal, but the same filed dropped directly onto the layout is incorrect, even though ComputerUsers 2::AssignmentDate is correct when dropped directly onto the layout.
So is my solution to simply use a one row portal in this case? It looks like the sort specified in the relationship between Computers_LastUser and ComputerUsers 2 does not carry through to the Users 2 occurance the way one might expect when fields from Users 2 are dropped directly onto the layout.
Why make it so complicated to just show the last user on a report.
I see two possibilities:
The first is that you are printing a one page report about one computer. In this case you only need to linke the table making the report to your computer table by any field such as computer to computer and use the X link in the popup. Drag a portal into its place and make it one line. Sort the portal by date in the order you want and there is your record.
The second is a real report made in the user table with the link to the loaner computer ids. Create a summary report using the computer id as a summary field for computer id and one for user id and then sort by computer id and date and user id.
This hasn't been debugged... :)
Actually, the report is an asset list report that should show all of the computer systems that we have as well as the last known user. Some computers will not have a user at all (servers, for example).