It's not a structural issue with a grid, it's the fact that a grid is awkward with the text heavy tables I'm working with....the grid...welll...to be frank, sucks for this type of table with memo fields, et al.

>>
>>>Hi, John! Sounds pretty familiar :). Did we discuss it before?
>>
>>Yes, I think I brought it up once before but the issue has reared its head again. I have a subtable that I want to browse through *without* a browse (there are memo fields) and I don't want a subform. So I was thinking of doing this container and I didn't want to reinvent the wheel.
>
>I don't think that separate container class is really needed. What prevents you from opening subtable with another alias and base grid on it?