>Darn, I was hoping it wouldn't come to that.

Yeah I know, but sometimes you just a get a situation the framework never expected... it happens. I'm sure you can kludge around it instead of overwrite, but I've found a flat out overwrite in a subclass where I leave a trail (i.e. copy/pasted code from parent) is actually easier to manage long term since I dont have to dig to refigure out why my kludge worked in the first place.

I would look at the FullListBizObj very closely to figure out the best place to get around this. The bizobj is handling everything related to the view, so that's the logical place for the alternative action that gets triggered when an empty result set comes back. Actually, it sounds like what you really need is a different alternative action for an empty result set... perhaps an dummy cursor for the list's record source that gives the user a indication/message that no records were found.

Keep me posted if you find a good way around this, interesting scenario... & good luck.