<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://www.infopathdev.com:443/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Qdabra Database Accelerator</title><link>https://www.infopathdev.com:443/forums/61.aspx</link><description>Qdabra Database Accelerator (DBXL) simplifies connecting InfoPath to SQL Server and SharePoint for codeless storage, permissions, workflow, and reporting on InfoPath forms. This forum also supports users of Qdabra's WSSP.</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP3 (Build: 31118.962)</generator><item><title>Re: Problems going from my infopath forms in sharepoint to dbxl as follows.</title><link>https://www.infopathdev.com:443/forums/thread/46900.aspx</link><pubDate>Sat, 12 Sep 2009 15:09:25 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:46900</guid><dc:creator>homeslacks</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/46900.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=61&amp;PostID=46900</wfw:commentRss><description>&lt;p&gt;Thanks Ernesto,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;I&amp;#39;ll spy out your advice/solution next monday and see how it goes.&amp;nbsp; &lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;:)&lt;/p&gt;</description></item><item><title>Re: Problems going from my infopath forms in sharepoint to dbxl as follows.</title><link>https://www.infopathdev.com:443/forums/thread/46892.aspx</link><pubDate>Fri, 11 Sep 2009 19:22:31 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:46892</guid><dc:creator>ErnestoM</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/46892.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=61&amp;PostID=46892</wfw:commentRss><description>&lt;p&gt;I think the problem is the SharePoint workflow. I think that if we remove that piece, the rest of the puzzle pieces will fit together nicely.&lt;br /&gt;&lt;/p&gt;&lt;p&gt;In general, these are the necessary steps:&lt;/p&gt;&lt;blockquote&gt;&lt;p&gt;1. Modify your InfoPath form template such that is submits to the DBXL Document service. Remove any connections that submit to SharePoint directly.&lt;/p&gt;&lt;p&gt;2. Create a new document type in DBXL using this xsn form.&lt;/p&gt;&lt;p&gt;3. Create SQL mapping.&lt;br /&gt;&lt;/p&gt;&lt;p&gt;4. Create SharePoint mapping. (Note: You can use the same SharePoint form library you were using, but DBXL needs to own the mapping, so you&amp;#39;ll need to empty the form library first and allow DBXL to recreate the documents. Of course, it&amp;#39;s safer to simply use a new SharePoint form library.) &lt;/p&gt;&lt;p&gt;5. Submit one document to test your SQL mapping and SharePoint mapping. Tweak (#3 and #4) as necessary until you are satisfied with the mappings.&lt;br /&gt;&lt;/p&gt;&lt;p&gt;6. Save your existing xml documents and import them into DBXL. &lt;a href="http://www.infopathdev.com/files/folders/document_deployer/entry46890.aspx"&gt;I wrote some steps today&lt;/a&gt; to cover one way to do this. The documents will be auto-mapped to SharePoint and SQL (but if they aren&amp;#39;t, a quick Reshred All will do it).&lt;br /&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;From reading your other questions, it seems like you need DBXL to perform a SharePoint-UPDATE operation; that is, DBXL needs to inherit the workflow and the existing library/documents. I don&amp;#39;t believe DBXL was designed specifically for that scenario, because DBXL needs to own the xml documents. Patrick wrote a blog post that may be related, but it concerns SQL. &lt;a href="http://www.infopathdev.com/blogs/patrick/archive/2008/07/09/using-dbxl-with-existing-databases.aspx"&gt;Read it here&lt;/a&gt;. Perhaps he can provide more of a philosophical perspective next week.&lt;/p&gt;</description></item><item><title>Problems going from my infopath forms in sharepoint to dbxl as follows.</title><link>https://www.infopathdev.com:443/forums/thread/46889.aspx</link><pubDate>Fri, 11 Sep 2009 18:32:13 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:46889</guid><dc:creator>homeslacks</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/46889.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=61&amp;PostID=46889</wfw:commentRss><description>&lt;p&gt;Long long long story short. I have forms in sharepoint that are happy ever after. They submit to sharepoint, have dataviews, run designer workflows etc. I need to migrate them to be submitted to DBXL then from dbxl to a SQL DB and to SP. No matter what I&amp;#39;ve done, no matter what sequence I follow I have issues. I have tried to many routes, have had so many issues it would be silly to list.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;My question is, what steps should I follow to get my current Infopath forms submitting to sharepoint to be submitted to DBXL so that DBXL submits them to SQL and to SP without hosing my solutions up. I know for one that I&amp;#39;ll be stuck with a DocID for the form name versus my very nice formatted form name, but I&amp;#39;ll deal with that.&lt;/p&gt;
&lt;p&gt;I know how and have without error created a form from scratch that submits to DBXL &amp;quot;only&amp;quot; and DBXL sends it to SQL and SP. That&amp;#39;s not an issue, it&amp;#39;s just when I have a form/template to start with that&amp;#39;s already published in sharepoint where things get thrashed.&lt;/p&gt;
&lt;p&gt;Any advice would be great being that I&amp;#39;m currently faced with DBXL only being good for new solutions.&lt;/p&gt;
&lt;p&gt;Thank you kindly.&lt;/p&gt;</description></item></channel></rss>