dbFront.com - Recent questions and answers in Version 1.1

Answered: Fixed: Lookup Details not displayed after foreign-key created

Fri, 27 May 2022 17:43:21 +0000

As of dbFront 1.2.2.2792, dbFront now correctly handles renamed/dropped fields that appear in lookups.

Previously it was determined that renaming a primary key or other column on a lookup table could cause dbFront to get confused and reject the relationship going forward due to the presence of now old invalid configuration.

This issues is now fixed.

If you ever encounter issues with relationships it is good to open the Log Viewer and search for the word "Relationship". dbFront should log any details there.

Answered: Fixed: Can't work out the rules to explain the search functionality

Thu, 30 Sep 2021 04:57:38 +0000

This issue has been fixed in dbFront version 1.1.5.0013.

dbFront "intelligently" allowed for full like searches on tables smaller than 10,000 rows but forced you to specifically enter %keyword% when the tables were larger. I realized this was causing confusion.

The reason for this functionality is that doing a [LIKE "%keyword%"] search automatically forces your database to perform a full table scan. For small tables this is manageable by a decent database server. On larger tables this can cause significant performance issues.

This update to dbFront adds a setting where you the Admin can decide at what point users need to manually use the %keyword% syntax. The setting FullLikeRowLimit is found in the [Help] / [Settings] dialog under the service tab. See: Default Wildcard

In addition this release of dbFront is smarter about distributing the search across the various columns, some of which might be full-text indexed and others which might not be.

If you need your users to perform full-text searches on larger tables (1 million rows+) then you may want to enable Full-Text search.

Answered: Disabled Action Button with Prompt Field of Passthrough on Read-Only record

Thu, 25 Mar 2021 02:47:01 +0000

This bug has been fixed by dbFront version 1.1.2.214.

Answered: AADSTS50011: The reply URL specified in the request does not match the reply URLs configured for the application

Tue, 12 May 2020 16:06:03 +0000

This error seems self-explanatory and should lead you to verify that the application URLs in Azure for your dbFront application are set up correctly.

One unusual situation can occur if your dbFront application is being projected by CloudFlare. In that situation, your dbFront application could be running as HTTP on your local server while the rest of the world sees HTTPS. For more details see: CloudFlare and dbFront

Answered: 405 - HTTP verb used to access this page is not allowed.

Tue, 12 May 2020 15:12:22 +0000

When the Single-Sign-On is enabled then dbFront sends the authentication requests to the service you have chosen.

When you have correctly signed in, then the Single-Sign-On service will attempt to send you back to dbFront with a POST request.

The error message "HTTP Error 405.0 - Method Not Allowed" means that the request was sent to a page that can't handle a POST request.

The most likely issue is that the URL you specified for your dbFront install is not correct. It is important that the URL ends with a "/" or "/default.aspx"

This error does not only apply to Google. It has also been reproduced with other vendors.

Depending upon your SSO vendor the URL might be named: "ACS URL", "Single sign on URL", or "Redirect URI".

The following are examples of valid URLs: