Y'know, there's another (very practical and very important) benefit that ADO has over remote views in some circumstances - tapping into cross-platform skills in an IS department or software shop. I'm working on a project right now for a company that develops with many types of technology. They understand that for this particular project, FoxPro makes a lot of sense. And, they even have a few FoxPro folks on hand to help maintain and extend our foxpro code. But they have a lot *more* VB and C++ programmers. Sitting in a meeting, trying to win the contract, we said we were going with ADO vs. remote views and every head in the meeting room began nodding happily. I am convinced we won the contract at that moment.

Okay, sure -- how much will this really help a VB'er trying to figure out our code in a year? Probably not too much. But even if this is just perception it is very important. When you are delivering an app and have total control over the architecture, you can say "let me worry about the inner workings." But in a lot of projects you need sign-off from folks who, for good reasons and bad, want the same technologies used in your work as they have in their other work.

Again, if we had said Remote Views we would not have gotten the contract. That alone makes me glad I work with ADO.