As for QB, so what???? For many developers, the main interest with QB is the export formats into something like SSIS....

The issue is that Intuit has succeeded in controlling 95% of the retail accounting market with a product that gives customers no choice whatsoever over development tool or database. That people make $ extracting the data into other comfort zones doesn't change this.

Now Intuit has converted their app from C++ to "something" that requires the NET runtimes and the rumor is that they plan to introduce new database options.

Intuit's shareholders want it to retain astonishing growth. Having secured 95% of one market, growth requires examination of other markets.

Seems to me that Kevin's customer exists in the "focus on outputs, not inputs" market in which Intuit already has been so successful. Both markets exist and both have plenty of $ for providers who understand their customers. It will be interesting to see whether Intuit can please its new target customers without burning off existing customers. They already survived one effort: the change from local files to a pseudo-C/S backend caused widespread protest from customers who were happy with local tables and didn't appreciate the "troublesome" new database.