DaDaBIK 5.1.1

DaDaBIK is a very popular and mature Open Source PHP application which allows you to easily create a highly customizable database front-end/application without coding. You can use it to create in a few minutes a very basic CRUD (create, read, update, delete) database front-end or to develop a more sophisticated database application. No programming skills are needed to use it; if however you are a PHP programmer with DaDaBIK you can save tens of hours of work. With DaDaBIK (differently from many competitors) you don`t produce a PHP script, which would become outdated when you modify the schema of your database, but instead you directly use its abstraction layer that can be easily updated every time you modify your database`s schema. DaDaBIK uses the ADOdb and the PDO database abstraction libraries in order to support as many DBMSs as possible, at the moment it has been tested on MySQL, PostgreSQL, SQLite, Oracle and MS SQL Server. The strength of DaDaBIK lies in its ability to be customized. For example for each table field you can choose:


  • if the field must be included or not in a search/insert/update form and results table

  • its label

  • its content format (e.g. numeric, alphabetic, e-mail, url...)

  • the HTML input type (e.g. textbox, menu, date, rich text editor, password box...)

  • the possible values, also driven from another table (foreign key support)

  • and more...


User's rating:

  • Currently 2.51/5
  • 1
  • 2
  • 3
  • 4
  • 5
Enlarge the screenshot of DaDaBIK
[ Enlarge Image ]
Download 1.9MB DaDaBIK

Download Direct

(1.9MB, Extension: PHP@FUNCTION=SHOW_DOWNLOAD)

Download alternate to DaDaBIK solution

Look at the free or trial alternatives and similar apps to DaDaBIK software by the tags. It's possible also to find substitutes for the most popular titles in the Software Development category.

| Database Front-end | Dadabik | Application |

History updates (Complete changelogs since the listing on this site)

5.1.1 [08-07-13]

New features The users page (admin area) has now a direct link to the users page (front-end). Fixed bugs If a web applications/site X, installed in the same domain as a DaDaBIK application Y, used a session variable name that also the dadabik application used, unexpected and risky effects could happen if the application X or another page set a PHPSESSID cookie valid also in the DaDaBIK application path (e.g. valid in the whole domain '/'). For example, if X (which could also be another DaDaBIK application) used the same session variable name to set the current "where clause" for a search, changing the "where clause" in one application could affect the "where clause" in the other. Now a new parameter (dadabik_session_name) is available in config.php in order to avoid this kind of problems. In some cases, for DaDaBIK ENTERPRISE, new users (created via DaDaBIK in addition to the default ones) could not log-in because DaDaBIK thought they were LDAP users (even if they were standard DaDaBIK users). In addition, the authentication type field was showed in the insert/edit form while it should not have been (in all versions). Fixed. If a field had the "Primary key field" set in form configurator but it was not a select_single field, DaDaBIK could produce unexpected results. Fixed. During insert if, for a select_single field without a linked table, a new element was added to the list ("other...") and the value of this element needed escaping (e.g. contained a '), even if the element was already available in the list it was added (resulting in a duplicated item). Fixed. The custom formatting functions were not applied individually to linked fields (select_single field type). Fixed (not fixed for CSV export, see later). DaDaBIK did not work correctly and could produce error messages in the following cases:
  • Insert or Search in a form having a select_single field whose linked table had read permissions set to MY
  • Edit of a record having a select_single field whose linked table had read permissions set to MY and having the selct_single field name different respect to the "Primary key field" parameter of the linked table
DaDaBIK could produce a "[08] Error: during query execution." message with some DBMS configurations when trying to install a table. Fixed. Page separators did not appear in the details page even if the parameter "Separator before this field (details page)" was set in form configurator. Fixed. In form configurator, the use of separator for options, linked fields and master/details (~ by default) whose length was more than 1 could lead to unexpected behaviours; now it is not possible anymore to save a separator having a length more than one. The bug has anyway been included in the known bugs for DaDaBIK applications which are already installed. DaDaBIK Enterprise didn't check if the dbms_type parameter was set in config. Fixed. Hungarian translation is now complete. The documentation has been slightly improved. The content of site_path parameter in config.php has been better clarified. Instructions about table inclusions have been improved, in particular it has been highlighted that if you want to delete a table from your DB you should first uninstall it in DaDaBIK and then drop it in your DB. New known bugs A new known bug has been added to the documentation: the content type formatting rules were not applied individually to linked fields (select_single field type) for CSV exporting. It will be fixed with DaDaBIK 6 because it requires core changes that we are going to apply anyway in DaDaBIK 6.

Other versions : 5.0 4.6 4.5 4.3

v5.0 [12-30-12]

Fixed bugs and other changes The documentation section about multiple instances of DaDaBIK has been (at least for the moment) removed. That section was not up-to-date and referred to a version of DaDaBIK which still didn't have the authentication feature: the result is that if users followed those instructions having authentication ON, a user authenticated on the first (not admin) instance could also access the /admin instance without authentication. This is not a proper bug but could lead to a false sense of security. Most of the language translations got corrupted after the 4.6 beta utf-8 move. Fixed. DaDaBIK could silently truncate some of the parameters values in interface configurator if the lenght of the parameter value length was greater than a threshold which depended on the parameter itself. Fixed. The null checkbox didn't work as expected (enabling/disabling input fields) because of a javascript error. Fixed. Prefix and defaut values didn't work correclty if they contained a double quote character. Fixed. The amount of time before a record is automatically unlocked is now 4 minutes (it was 2). Authentication is now enabled by default. The Russian language was not specified in the languages list to choose from (config.php). Fixed. A re-installation of DaDaBIK on the same database didn't clean-up the table containing the information about the installation itself. Fixed. This bug shouldn't have had any effect on the user side, though. The importance of the parameter $site_path for security reasons has been highlighted in config.php. The authentication section of the Documentation was not clear. Improved. Due to SQLite limitations, the script for upgrading DaDaBIK to a new release is not anymore available for SQLite. The following fix was implemented in 4.6 beta but the quotes in the sentences appeared corrupted in the change log, so re-post: Table or field names having the string "from" in the name could lead to query execution error with SQLite. Fixed. The following fix was implemented in 4.6 beta but didn't appear in the change log, so re-post: The installation of views diddn't work with MySQL and PostgreSQL. Fixed.

v4.6 [11-06-12]

Fixed bugs and other changes The documentation section about multiple instances of DaDaBIK has been (at least for the moment) removed. That section was not up-to-date and referred to a version of DaDaBIK which still didn't have the authentication feature: the result is that if users followed those instructions having authentication ON, a user authenticated on the first (not admin) instance could also access the /admin instance without authentication. This is not a proper bug but could lead to a false sense of security. Most of the language translations got corrupted after the 4.6 beta utf-8 move. Fixed. DaDaBIK could silently truncate some of the parameters values in interface configurator if the lenght of the parameter value length was greater than a threshold which depended on the parameter itself. Fixed. The null checkbox didn't work as expected (enabling/disabling input fields) because of a javascript error. Fixed. Prefix and defaut values didn't work correclty if they contained a double quote character. Fixed. The amount of time before a record is automatically unlocked is now 4 minutes (it was 2). Authentication is now enabled by default. The Russian language was not specified in the languages list to choose from (config.php). Fixed. A re-installation of DaDaBIK on the same database didn't clean-up the table containing the information about the installation itself. Fixed. This bug shouldn't have had any effect on the user side, though. The importance of the parameter $site_path for security reasons has been highlighted in config.php. The authentication section of the Documentation was not clear. Improved. Due to SQLite limitations, the script for upgrading DaDaBIK to a new release is not anymore available for SQLite. The following fix was implemented in 4.6 beta but the quotes in the sentences appeared corrupted in the change log, so re-post: Table or field names having the string "from" in the name could lead to query execution error with SQLite. Fixed. The following fix was implemented in 4.6 beta but didn't appear in the change log, so re-post: The installation of views diddn't work with MySQL and PostgreSQL. Fixed.

v4.5 [09-20-12]

Fixed bugs

In some cases you could get a "Specified key was too long; max key length is 1000 bytes" or similar error during installation. Fixed. Thanks to Alonzo for having reported it. Furthermore, in some cases (probably quite uncommon), where a table name or its unique field name or a unique field record value are longer than expected, the record locking feature could work not correctly. Now DaDaBIK produces an error if the lenght is not supported. Using the rich_editor field type led to incorrect search results because the HTML editor add fomatting tags by default to the search text. Now a normal textearea is used for search forms to avoid this behavior. Thanks to user Funbird for the report. Please note that, still, the formatting tags inserted in a field through the HTML editor are not filtered so if you search "hey good" and you have "hey good morning" in your DB, of course you won't find it. This has been added to the "unexpected behaviors" section of the documentation. The "refresh installation" operation lost settings about master/details views: table and linked items. Fixed. DaDaBIK had a typo in the German translation. Fixed. (Thanks Heinz for the report) A bug about the default date 1968-01-01 was listed in the "Known bugs" documentation section even if it was already solved. Fixed. Choosing Estonian as language led to a parse error message. Fixed. Other changes During installation, a warning message is now displayed about the risks of enabling the CSV export feature in a public site. A note in the documentation has also been added. Thanks to user dh for having reported it. A minor bug about record editing when an identifier field value is changed has been added to the known bugs section of the documentation.

v4.3 [03-13-12]

Average review rating :

Useful independent reviews and opinions of the users

Review DaDaBIKWrite a review « Be the first to post a review for DaDaBIK download!

Predicted future versions and notices:

The doDownload.com constantly monitors the update of all programs, including information from the DaDaBIK 5.1.2 changelog file, however sometimes it can happen that data are not complete or are outdated.We assume that author continue's to develop 5.2.0 version with further advanced features, and soon you will be informed. Equally important 6.0.0 upgrades of the program we will continue to monitor. Full DaDaBIK description has been compared with the overall software database and our algorithm has found the following applications (are showed below).