dbFront.com - Recent questions and answers in Version 1.2

Error: There is already an open DataReader associated with this Connection which must be closed first.

Wed, 07 Feb 2024 15:27:42 +0000

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.

Error: Can't run customProcedureName(), There is already an open DataReader associated with this Command which must be closed first.

What does this error mean and how can I fix it.

Answered: A new row does not appear in the lookup form

Tue, 29 Aug 2023 20:23:12 +0000

To Cache or not to Cache, that is the question.

This issue is because dbFront attempts to use caching to improve the application responsiveness.

Therefore all lookup results are only refreshed if dbFront recognizes an update from within dbFront, or at the database (very slow), or periodically.

Disable Caching

If you know that a table will receive regular updates outside dbFront, then the best solution is to disable the caching.

There are two methods:

Disable Server Lookup, and
Change the table caching type.

For more details see: https://dbfront.com/qa/1012/force-dbfront-to-load-a-fresh-copy-of-the-data-everytime

Answered: FIXED: Maximize buttons not displaying properly with latest Chrome update

Mon, 04 Jul 2022 21:15:40 +0000

This issue is due to a Chrome browser update that affects nearly all versions of dbFront. As you likely know, Edge is now a variant of Google's Chrome.

This issue also affects the position of the gear icons, lookup dropdowns and other items.

The latest Feature release of dbFront 1.2.2.2792 already contains the fix to this browser change.

I have also released a patch version of 1.1.5.6687 to fix this same issue. The changes to dbFront are trivial and safe.

All that is required is a small addition to the base CSS file. You can update the file ccs/Site.css and add the following three lines.

div.detailFields div.value {
   position: relative; /* Fixes gear, lookup and notification positioning */
}

Answered: Implicit conversion ... cannot be performed because the collation of the value is unresolved due to a collation conflict

Fri, 22 May 2020 14:24:23 +0000

PROBLEM

dbFront concatenates fields for the table caption and also for lookup display values.

The issue is that dbFront is concatenating fields in your table that have different non-default collations set.

For example, your table might be set with a collation of "DanishNorwegianCIAS", but one or more of your table columns might have a non-default collation set to "SQLDanishPrefCP1CIAS".

SOLUTION

Since this is SQL Server, the best solution is to create a computed table column that concatenates the fields as you would like them while automatically dealing with the collation issues.

For example, you could create a computed column named [DisplayName] and set the computed column expression to:

(
  isnull([UserName], '')
  + ', ' + isnull([FirstName], '')
  + ', ' + isnull([LastName], '')
  COLLATE DATABASE_DEFAULT
)

The key piece to add is "COLLATE DATABASE_DEFAULT". This tells your database server to automatically use the default collation. Your specific collation needs may be different.

An additional benefit of computed columns, is that you can do much more then a simple concatenate.

Once you have created the computed column you can then update the table caption and the lookup columns so that they only use your new [DisplayName] column.