I’ve gotten quite a bit further, though I’m still not there.
I wish somebody had told me before that when you add a method to a query in the AOT, that method is actually a QueryRun method.
Now that I’ve discovered this, linking the Query to my inmemory table of choice is not so much of a problem anymore: I just overrode init on the QueryRun and used setCursor to do the trick (although I have no clue whether I should do that before or after the “super” call in init; for safety, I did both).
Unfortunately, although I can check that the temp table I pass to setCursor does contain records, it looks like the grid on the listpage is not connected to this new instance of the table: it continues to show no records.
Does anybody have a suggestion on what to try next?
might I have more success by using a tempdb table instead of an inmemory one? (note: because of some details in the construction, this would actually require quite a bit of work, so I’m somewhat hesitant)
should I move the setCursor call to somewhere else?
is there some magic call to make the grid “update” itself to the new table instance?