<?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: DBXL Help</title><link>https://www.infopathdev.com:443/forums/thread/59148.aspx</link><pubDate>Wed, 22 Sep 2010 13:33:25 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:59148</guid><dc:creator>ErnestoM</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/59148.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=61&amp;PostID=59148</wfw:commentRss><description>&lt;p&gt;&amp;nbsp;If I have understood the scenario correctly, you have one installation of DBXL and want to use it as both Dev and Production.&lt;br /&gt;&lt;br /&gt;To accomplish this, you’ll need two doctypes and two sets of tables. So let’s begin with the DEV tables. Let’s assume your DEV document type will map data to these three tables.&lt;br /&gt;&lt;br /&gt;•&amp;nbsp;&amp;nbsp; &amp;nbsp;DEVTable1&lt;br /&gt;•&amp;nbsp;&amp;nbsp; &amp;nbsp;DEVTable2&lt;br /&gt;•&amp;nbsp;&amp;nbsp; &amp;nbsp;DEVTable3&lt;br /&gt;&lt;br /&gt;In the database tab for the DEV document type, you can control where the data gets shredded, simply select the specific tables (the DEV tables).&lt;br /&gt;&lt;br /&gt;Once developed and tested, you want to create your “production” document type and tables. You can create tables with the same structure but remove the DEV prefix.&lt;br /&gt;&lt;br /&gt;To create the production document type, click EDIT for the DEV document type. You’ll see a Save As button at the top. This will allow you to create a new document type, with the same XSN and database mapping, but with a different name. &lt;br /&gt;&lt;br /&gt;Give the doctype a new name, and clik Save. This new doctype (“production”) will contain the same database mapping, though you’ll need to update the table names due to the removal of the DEV prefix in SQL.&lt;/p&gt;&lt;p&gt;You can control where the xml data is mapped by changing the data connection string. So you could have two document types, with the same xsn and the same mapping, but using two different connection strings. One will be dev/test and the other can be production.&lt;/p&gt;&lt;p&gt;Hopefully I’ve understood the question… let us know if you have any questions on this.&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;</description></item><item><title>DBXL Help</title><link>https://www.infopathdev.com:443/forums/thread/59090.aspx</link><pubDate>Tue, 21 Sep 2010 14:02:06 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:59090</guid><dc:creator>RSharepoint</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/59090.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=61&amp;PostID=59090</wfw:commentRss><description>&lt;p style="MARGIN:0in 0in 0pt;" class="MsoNormal"&gt;&lt;font size="3" face="Calibri"&gt;Hi ,&lt;/font&gt;&lt;/p&gt;&lt;font size="3" face="Calibri"&gt;&amp;nbsp;&lt;/font&gt; 
&lt;p style="MARGIN:0in 0in 0pt;" class="MsoNormal"&gt;&lt;font size="3" face="Calibri"&gt;&amp;nbsp;We have purchased the Basic version of DBXL &amp;nbsp;Database Accelerator.&lt;/font&gt;&lt;/p&gt;&lt;font size="3" face="Calibri"&gt;&amp;nbsp;&lt;/font&gt; 
&lt;p style="MARGIN:0in 0in 0pt;" class="MsoNormal"&gt;&lt;font size="3" face="Calibri"&gt;We have been able to successfully install DBXL in our &amp;nbsp;production server.&lt;/font&gt;&lt;/p&gt;&lt;font size="3" face="Calibri"&gt;&amp;nbsp;&lt;/font&gt; 
&lt;p style="MARGIN:0in 0in 0pt;" class="MsoNormal"&gt;&lt;font size="3" face="Calibri"&gt;The DBXL is installed on the same server where SharePoint is installed and the SQL instance used by DBXL is on another machine.&lt;/font&gt;&lt;/p&gt;&lt;font size="3" face="Calibri"&gt;&amp;nbsp;&lt;/font&gt; 
&lt;p style="MARGIN:0in 0in 0pt;" class="MsoNormal"&gt;&lt;font size="3" face="Calibri"&gt;For now, we have only one XSN that we want to shed the data to SQL Server using DBXL.&lt;/font&gt;&lt;/p&gt;&lt;font size="3" face="Calibri"&gt;&amp;nbsp;&lt;/font&gt; 
&lt;p style="MARGIN:0in 0in 0pt;" class="MsoNormal"&gt;&lt;font size="3" face="Calibri"&gt;We plan to set up and Test everything in the Development Server before we move it to the Production.&lt;/font&gt;&lt;/p&gt;&lt;font size="3" face="Calibri"&gt;&amp;nbsp;&lt;/font&gt; 
&lt;p style="MARGIN:0in 0in 0pt;" class="MsoNormal"&gt;&lt;font size="3" face="Calibri"&gt;My question is:&lt;/font&gt;&lt;/p&gt;
&lt;p style="MARGIN:0in 0in 0pt;" class="MsoNormal"&gt;&lt;font size="3" face="Calibri"&gt;&amp;nbsp;How can I use &amp;nbsp;XSN’s as a test document types in the development server?&lt;/font&gt;&lt;/p&gt;
&lt;p style="MARGIN:0in 0in 0pt;" class="MsoNormal"&gt;&lt;font size="3" face="Calibri"&gt;Is there a way I can use a different instance of SQL in Development server without affecting the live database?&lt;/font&gt;&lt;/p&gt;&lt;font size="3" face="Calibri"&gt;&amp;nbsp;&lt;/font&gt; 
&lt;p style="MARGIN:0in 0in 0pt;" class="MsoNormal"&gt;&lt;font size="3" face="Calibri"&gt;Please advice.&lt;/font&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;</description></item></channel></rss>