Update: setting the suspect subform's recordsource in form design rather than dynamically, using identical SQL syntax, eliminates the above error message, but drops the required functionality, which as I say works just fine as long as one stays in form view.
There is evidently something...