<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>dbFront.com - Recent questions in Version 1.2</title>
<link>https://dbfront.com/qa/questions/errors/version-1-2</link>
<description>Powered by Question2Answer</description>
<item>
<title>Error: There is already an open DataReader associated with this Connection which must be closed first.</title>
<link>https://dbfront.com/qa/1378/error-there-already-datareader-associated-connection-closed</link>
<description>&lt;p&gt;I have this stored procedure button that ran once just fine, but now I get the below error when I try to run it. I tried restarting the dbFront service but it's still occurring.&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Error: Can't run customProcedureName(), There is already an open DataReader associated with this Command which must be closed first.
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;What does this error mean and how can I fix it.&lt;/p&gt;
</description>
<category>Version 1.2</category>
<guid isPermaLink="true">https://dbfront.com/qa/1378/error-there-already-datareader-associated-connection-closed</guid>
<pubDate>Wed, 07 Feb 2024 15:27:42 +0000</pubDate>
</item>
<item>
<title>A new row does not appear in the lookup form</title>
<link>https://dbfront.com/qa/1325/a-new-row-does-not-appear-in-the-lookup-form</link>
<description>&lt;p&gt;We have a table that provides lookup values.  When the user addeds a new entry they click the box and the rows of the table are displayed for selection.  Very standard.  We added a new row to add a new selectable option and the new row will not appear in the lookup.  I have tried looking at the base table and it does show the new entry but it does not appear in the dropdown.  I have also tried turning caching off on the table but still nothing.&lt;/p&gt;
&lt;p&gt;is there a way force a refresh of the lookup table? &lt;/p&gt;
</description>
<category>Version 1.2</category>
<guid isPermaLink="true">https://dbfront.com/qa/1325/a-new-row-does-not-appear-in-the-lookup-form</guid>
<pubDate>Fri, 07 Jul 2023 16:51:00 +0000</pubDate>
</item>
<item>
<title>FIXED: Maximize buttons not displaying properly with latest Chrome update</title>
<link>https://dbfront.com/qa/1205/maximize-buttons-displaying-properly-latest-chrome-update</link>
<description>&lt;p&gt;So with the latest revision of Chrome and by extension Edge, the Maximize button that normally would be next to the dropdowns for the relationship key pairs display on the webpage in strange places.  Was on an older version of DBFront and thinking I needed to upgrade to fix this issue.  So currently upgraded to latest version 1.2.1.1145, this did not fix the issue.  Working in old IE, no issue. &lt;/p&gt;
</description>
<category>Version 1.2</category>
<guid isPermaLink="true">https://dbfront.com/qa/1205/maximize-buttons-displaying-properly-latest-chrome-update</guid>
<pubDate>Fri, 10 Jun 2022 18:03:01 +0000</pubDate>
</item>
<item>
<title>Implicit conversion ... cannot be performed because the collation of the value is unresolved due to a collation conflict</title>
<link>https://dbfront.com/qa/719/implicit-conversion-performed-collation-unresolved-collation</link>
<description>&lt;p&gt;When I open a table in dbFront I get the following error:&lt;/p&gt;
&lt;p&gt;Can't get data, Implicit conversion of varchar value to varchar cannot be performed because the collation of the value is unresolved due to a collation conflict between &quot;DanishNorwegianCIAS&quot; and &quot;SQLDanishPrefCP1CIAS&quot; in add operator.&lt;/p&gt;
&lt;p&gt;How do I resolve this error?&lt;/p&gt;
</description>
<category>Version 1.2</category>
<guid isPermaLink="true">https://dbfront.com/qa/719/implicit-conversion-performed-collation-unresolved-collation</guid>
<pubDate>Fri, 22 May 2020 13:45:31 +0000</pubDate>
</item>
</channel>
</rss>