Perhaps he could add an INSERT trigger to the table in question and record appropriate information elsewhere about the row(s) being inserted.
I'm having trouble resisting launching off onto my rant about the concept of "last" when applied to a table in a relational database. Without some sort of information on which to order the row so the concept of "last" has some meaning, the OP has a real problem.
A trigger could store the current_timestamp when the row was inserted. Ordering on that would allow "last" to have a meaning.
Custom Apps, Inc.