Yes, correct. Sorry I was not thinking clearly when I supplied you that link earlier. My bad. I should have directed you to the second installation option in the first place (instructions are in the docs for the program). In my installations, I've taken a simpler approach to the dual installation by making copies of the pertinent files (index.php, config.php, admin.php - if memory serves correct, those are the only ones needed for a second install on the same DB). Then just make the appropriate changes in those files to point to the related files and rename them all to indexAdmin.php, configAdmin.php and adminAdmin.php (or something similar).
With this model, you need only one set of DaDaBIK internal tables and a second dadabik_table_list (dadabik_admin_table_list for example) to control specific aspects/permissions of each table in the database.