Dear John

>>Having grid columns not correspond to the physical position of the underlying recordsource is not what I would call an optimal implementation.<<

Surely you jest. The grid can and does allow sophisticated developers to structure column setup to meet customer need. See that word "customer"? customers do not give a jot about the underlying datasource. They care that columns are positioned to their satisfaction. Try telling customers that it is "optimal" to position columns differently from what they want and you'll find out how clever your ideas are.

>>If one has the slightest clue of the inherent problems and finkyness of the grid control, one would shy away from this practice. Anything else is asking for trouble.<<

What a load of FUD. The grid may not be perfect, but setting up columns to make a customer happy or improve functionality, is not "asking for trouble"!

If the grid were *really* as inflexible and useless as you seem to want, there would have been a riot long ago IMHO. No choice of column position except as in the datasource? Unable to leave a column out? Sounds absolutely awful.

As for your "legal" arguments, you can spout words like "adjudge" all you like, but behind it all you are still pushing an argument past logic to an absurd position.

Regards

JR