>>It shouldn't be that way - databinding is not rocket science.
>>An over reliance on databinding can also constrict the design paradigm. Developers relying on databinding (as those hey-day consultants of the 90's relied on grids [or browse windows]) will end-up with low integration projects (one form - one table).
>
>What are you talking about?

What are you talking about, Rick?

Your write service and tier programs. You are probably the greatest MS inside outsider that ever hit the firewall - but lets be clear - you do not design, write or implement end user GUIs and file structures - you market (I guess from the way you're painting the board, that your business plan is moving from ASP to NET) and write tier tool modules for developers.

So I need some convincing from you in this regard - you have a narrow yet deep understanding of a little piece of the software universe. You've done real good at it - but I have not yet seen any proposals or support for those of us developing desktop GUIs. Even when I had questions about FOXISAPI and IIS, you were never there, except to talk around possible alternative solutions using one of you products.

Lets be clear - if a prospect needed a house/book keeping project specified , designed, bugeted and scheduled - you would be one of the last people I would expect to see there.

Are you writing desktop apps now as a sideline? Maybe there's some databinding comparisons you've made with the GUIs for your tier engines - but those GUIs are a lot different than the GUIs and responsibilities of a full blown end user accounting interface. Aren't they?