From the error you described, there is clearly a bit more going on here that just returning the last row of a relatively simple dataset.  You may need to get more specific, if these solutions don't help.

A couple of questions, first.  Do you need the entire last row, or just the greatest date?  Are you using the other rows in the report, or can you afford to have the report only return the last row?  Where on the report (i.e., in what section) are you trying to use this information?

Am I correct in understanding that an account can have multiple records for the same date, and that in such a case we look at the sequence field to sort within the date?

If you do want just the last row on the report, and don't care about the rest of the data, then I would perform this operation in SQL.  It's a relatively simple self-join operation there, and you can find the details in any SQL book (or I can provide it, if you need).

If you are returning all the rows, and need to pull out the last record for additional display purposes, you have several options.  The simplest is to create a new details section, with a formula to suppress that looks like:

{MyReport.MyDate} <> Maximum({MyReport.MyDate}) OR {MyReport.Sequence} <> Maximum({MyReport.Sequence})

If you need to reference it in a group footer, you can try a few things.  One is to use a SQL Expression to retrieve the information.  This may be harder than you want to go with, though.  You can create a series of global variables, and store the data in them when the maximum record is evaluated.  This approach may create issues with timing, depending on what you're doing with this information.  You can simply sort all of your records appropriately, in which case the "current" record when processing the group footer is the last record.  This method is not always reliable, though.

If you need to reference multiple "last" records, and do some kind of analysis on them, I would strongly recommend using a subreport.

That does seem to clarify the situation.

I would go with a SQL solution.  If possible, change the query in your database.  If that's not possible, use the Add Command feature when creating your datasource to enter a SQL query.

Your query should look something like:

SELECT Main.*
FROM MyTable Main
JOIN (SELECT AccountID, 
         MAX(QueueDate) AS MaxDate
         FROM MyTable
          GROUP BY AccountID) Filter
ON Main.AccountID = Filter.AccountID
AND Main.QueueDate = Filter.MaxDate

Obviously, your solution will actually be a bit more detailed.  But hopefully that should give you a push in the right direction.