re: InfoPath Forms 101: Codeless = Less Cost

Patrick Halstead — Wed, 28 Apr 2010 21:44:44 GMT

Hi Sunjay,

Sorry for the delay in responding. Basically, for SharePoint 2010, the same gaps exist and DBXL is still needed to codelessly submit XML forms to SQL. You can submit flat lists to SharePoint and using BCS push and pull that data to SQL but to do repeating tables and rich data types, you still need a Web Service and that's what DBXL provides. DBXL is a generic data-driven Web service, so you can change your XSN data source or the tables in SQL and it won't break the submission process. qRules is still needed to fill all of the gaps in InfoPath where you need to write code - qRules lets you do a bunch of cool things without writing code, just use rules to access the functionality. I hope that answers your question. Of course, we'd be happy to discuss it further with you.

re: InfoPath Forms 101: Codeless = Less Cost

Sunjay — Wed, 24 Mar 2010 16:43:14 GMT

hi patrick

totally agree. Now i have a quick question or a comment. How does Qdabra DBXL/Q Rules differ in the SP 2010? meaning that InfoPath 2010 is integrated with SharePoint forms, so what is the story to tell the users why Q DBXL/Q Rules. Sure i have played with InfoPath 2010, but then every ones playing with a toy is different than actually working it. I am trying to leverage Infoapth with Q DBXL and just wanted to know going forward what is the USP for Q DXL. Would higly appreciate your thoughts on this.

TIA