>Performance may not be a problem now, but when it becomes a problem you'll have to change your code. Why not find a method that works in most cases? SQL is the answer.

Mike,

I tried this idea, but I had lots of problems, one of them is grid reconstruction, which requires some special code (using Vlad's FAQ).

Basically, I have one main grid. Another is a 'child' grid. Do I need to create a view for the child (temp view, I don't want to keep it in a database) and requery it while navigating on the parent table?

Thanks in advance.