>Actually, if I see a business situation that looks like different items are requiring such different sets of data, I put them in separate tables. IOW, a Product does not belong in the same table as a Service Item, because they hold entirely different sets of data.

I don't think so - they are both line items - and can end up in the same grid on the same invoice on the same reports, etc etc etc. In other words - they are NOT entirely different sets of data - rather, the same, only with one needing additional info. In fact, since they probably share a LOT of fields (qty, description, fkey, etc) - that weakens your argument.

I would submit that if you do this, you are causing yourself a lot more headaches in multiple grids, reports, etc. than just to do it with a 1-to-1. however - if you constrain yourself with RV - I can see why you wouldn't. Sometimes one less than optimal practice will force you into others to cover for the first eh? ;-)

> we _do_ have different data modelling philosophies.

Alas! - we agree on something!

Thanks,