Sorry so late in responding - been a little ill and out of the office...

This problem came up when I tried to convert our existing VFP8 app to VFP9. There are two tables that are linked with a primarykey - each match should result in an average of 3 to 8 records in the child table for every record in the parent table. There are 2,223,000 records in the child table and 605,000 in the parent table.

The view that used to work no longer does. That's when I began trying to produce code to reproduce the problem. I'll try to make it more "real world" if that's what you need. I imagine there would need to be more records in both table - really don't know. I'll play around with it some and see what I can come up with.


>I see Aleksey has responded on this issue and has logged it in our internal tracking system.
>
>But, besides that, how realistic is this scenario? You have two tables of 600,000 records that you're joining on a fields that contain blanks, setting up a situation where there's an unholy number of possible combinations.
>