if you rowsource, instead of additem to list controls, you loose the ability to drag and drop.

Incorrect. The VFP 3 CodeBook and Jayesh Patel's .NET mover both demonstrate drag and drop capability, and both use binding.

With table buffering interfaces the is a tendacy to write one file forms. In those kinds of projects there are usually a plethora (i had to say it) of cascading modal forms that ultimately drill down to "the" form that initiates an action.

There can be a 'tendancy' towards anything. I've seen just the opposite: table buffering used in multi-table data maintenance forums. Regardless, the capability in itself doesn't promote either practice. And contrary to your incessant references, the presence of grids in an app doesn't make app shallow.

If you rely on rowsource binding - there is a high likelyhood that you would refrain from OCX navigators (tree and list) because OCX list navigators are not bound - they require discrete instructions to populate. It's not big deal - unless we refrain because binding is so much easier. The result - our projects end up wordy, formy, temp file monsters - they end up ugly.

While you're partly right on the OCX nav tools, this is a ridiculous conclusion.

Admittedly, I stopped reading after you ranted on for the hundredth time about ".NOT".

Rick's a big boy, he can defend himself very well on his own - I just think it's astounding that you would pass a judgement on Rick's knowledge, given your grasp of certain facts.

Terry, if you're doing this purely for entertainment value, if you derive pleasure from these types of posts, fine. But if you're actually serious about what you say, then you really need to learn how to frame your arguments better.