<?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: Question about using DBXL QueryDB from SharePoint page</title><link>https://www.infopathdev.com:443/forums/thread/61373.aspx</link><pubDate>Fri, 12 Nov 2010 17:00:53 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:61373</guid><dc:creator>Catharine</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/61373.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=61&amp;PostID=61373</wfw:commentRss><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;I have been doing some investigation and think I have got to the bottom of it....&lt;/p&gt;
&lt;p&gt;It is not the data connection which is causing the problem.&lt;/p&gt;
&lt;p&gt;Some time ago I got a file InfoPathOpen.js from you.&amp;nbsp; To be able to click on a hyperlink for an infopath file without getting prompted to open the file.&amp;nbsp; Put that on the server as suggested and put a &amp;lt;script type=&amp;quot;text/javascript&amp;quot; src=&amp;quot;.... reference in the form.&lt;/p&gt;
&lt;p&gt;I obviously put it in the wrong place... I could access it but not all of the users.&amp;nbsp; I have now moved it and got rid of the 3 prompts. Phew !&amp;nbsp; Thank you for your help.&lt;/p&gt;
&lt;p&gt;Catharine.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;</description></item><item><title>Re: Question about using DBXL QueryDB from SharePoint page</title><link>https://www.infopathdev.com:443/forums/thread/61368.aspx</link><pubDate>Fri, 12 Nov 2010 15:17:37 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:61368</guid><dc:creator>Jimmy</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/61368.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=61&amp;PostID=61368</wfw:commentRss><description>&lt;p&gt;DBXL doesn&amp;#39;t allow anonymous access, and from what I can find, the &amp;quot;Don&amp;#39;t attempt to authenticate&amp;quot; option is designed to prompt for a password when anonymous access doesn&amp;#39;t work.&amp;nbsp; Have you tried the Windows authentication option?&lt;/p&gt;</description></item><item><title>Re: Question about using DBXL QueryDB from SharePoint page</title><link>https://www.infopathdev.com:443/forums/thread/61360.aspx</link><pubDate>Fri, 12 Nov 2010 13:27:04 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:61360</guid><dc:creator>Catharine</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/61360.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=61&amp;PostID=61360</wfw:commentRss><description>&lt;p&gt;Hi, &lt;/p&gt;
&lt;p&gt;The problem is nothing to do with InfoPath.&lt;/p&gt;
&lt;p&gt;The problem occurs when opening a SharePoint screen which has a data connection to a DB via DBXL Query DB. - It is not opening any Infopath form.&lt;/p&gt;
&lt;p&gt;The problem still exists.&lt;/p&gt;
&lt;p&gt;Catharine&lt;/p&gt;</description></item><item><title>Re: Question about using DBXL QueryDB from SharePoint page</title><link>https://www.infopathdev.com:443/forums/thread/61358.aspx</link><pubDate>Fri, 12 Nov 2010 12:51:48 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:61358</guid><dc:creator>Patrick Halstead</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/61358.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=61&amp;PostID=61358</wfw:commentRss><description>&lt;p&gt;Hi Catharine,&lt;/p&gt;
&lt;p&gt;Trusted doesn&amp;#39;t work for .NET and that applies to InfoPath forms with code. Your form has a lot of code so please remove from Trusted and add to Local Intranet and let us know if that fixes your issue.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m going offline now but Ernesto and the rest of the support team will be around to respond.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;</description></item><item><title>Question about using DBXL QueryDB from SharePoint page</title><link>https://www.infopathdev.com:443/forums/thread/61351.aspx</link><pubDate>Fri, 12 Nov 2010 10:22:13 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:61351</guid><dc:creator>Catharine</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/61351.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=61&amp;PostID=61351</wfw:commentRss><description>&lt;p&gt;I have DBXL 2.3.&amp;nbsp; &lt;/p&gt;
&lt;p&gt;I have a SharePoint page in which I have a data table.&amp;nbsp; The data table is populated&amp;nbsp;by a call to qdabrawebservice/querydb.asmx.&amp;nbsp; using the GetCloumnsXMLStrQuery. (Login is set to Don&amp;#39;t attempt to authenticate.)&lt;/p&gt;
&lt;p&gt;This works very well for me.&amp;nbsp; However when I release it to other users they are being prompted for their username and password three times before the screen opens and displays the data.&amp;nbsp; The same is true if they refresh the screen.&lt;/p&gt;
&lt;p&gt;The users are in the correct permissions groups for the site/page, other pages without data connections on the same site are fine.&amp;nbsp; So I can only conclude that it is the data connection that is causing this.&lt;/p&gt;
&lt;p&gt;Users may have either IE8 or IE6.&amp;nbsp; We have tried putting the SharePoint site into the Trusted list in IE. and this does not solve the issue.&lt;/p&gt;
&lt;p&gt;Does anyone have any ideas about what the issue could be - or where I can start looking ?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The permissions area of&amp;nbsp;my Web.config for DBXL looks like - is there something missing ?&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;lt;permissions&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;groups useGlobalPermissions=&amp;quot;true&amp;quot;&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;group name=&amp;quot;Readers&amp;quot;&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;alias name=&amp;quot;&amp;quot; /&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;/group&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;group name=&amp;quot;Writers&amp;quot;&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;alias name=&amp;quot;&amp;quot; /&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;/group&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;group name=&amp;quot;Admins&amp;quot;&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;alias name=&amp;quot;BUILTIN\Administrators&amp;quot; /&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;/group&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;group name=&amp;quot;DbxlAdmins&amp;quot;&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;alias name=&amp;quot;BUILTIN\Administrators&amp;quot; /&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;/group&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;/groups&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;providers&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;!-- Add a connectionString attribute to the provider if it uses something besides the DBXL database --&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;!-- connectionString=&amp;quot;Integrated Security=SSPI;data source=(LOCAL)\SQLEXPRESS&amp;quot; --&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;provider name=&amp;quot;QdFlow&amp;quot; type=&amp;quot;Qdabra.Dbxl.QdFlow.PermissionProvider, Qdabra.Dbxl.QdFlow&amp;quot; connectionString=&amp;quot;Data Source=rudb001;Initial Catalog=QdabraSamples;Integrated Security=True&amp;quot;&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;doctypes&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;doctype name=&amp;quot;QdEmailFlow&amp;quot; /&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;/doctypes&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;/provider&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;!-- The below syntax is used to exclude one doctype from using the handler &lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;All other doctypes are included by default using an exclusion rule&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;--&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;!-- EXAMPLE --&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;!-- &amp;lt;provider name=&amp;quot;SpecialPermHandler&amp;quot; type=&amp;quot;Customer.SpecialPermHandler&amp;quot;&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;doctypes exclusionRule=&amp;quot;true&amp;quot;&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;doctype name=&amp;quot;TestForm&amp;quot;/&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;/doctypes&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;/provider&amp;gt;--&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;!-- The below syntax is used to include one doctype (and by default exclude all others) --&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;!-- &amp;lt;provider name=&amp;quot;SpecialPermHandler&amp;quot; type=&amp;quot;Customer.SpecialPermHandler&amp;quot;&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;doctypes exclusionRule=&amp;quot;false&amp;quot;&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;doctype name=&amp;quot;TestForm&amp;quot;/&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;/doctypes&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;/provider&amp;gt;--&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;/providers&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;lt;/permissions&amp;gt;&lt;/p&gt;
&lt;p&gt;Thank you.&lt;/p&gt;
&lt;p&gt;Catharine&lt;/p&gt;</description></item></channel></rss>