>Chris --
>
> Are you linking the parent/child tables in the report environment or are you using a SQL query to create one cursor and report off of that?
>
> I use the 2nd approach. I've heard of idiosyncracies with the 1st approach similar to what you're describing that are eliminated by using a query.

All the tables are set up in the form's private datasession. I'm corrupting the preferred Mere Mortals method of invoking a report by having it use the already open and prepped tables rather than reopening (and reloading and retweaking) them in a separate data session.

A last second SQL statement might be simpler than creating a separate view.