I'm having some trouble visualizing how this whole system works and the documantation doesn't help any. I've been using DBMan (the text file version) for several years and I was under the impression DBMan SQL was the same thing but for SQL instead of text files. In DBMan you set up the default.cfg (or whatever you called the database) and that defines the layout of your data entry forms. When you access the db.cgi script you simply supply the db you want to in the URL and the script loads the proper cfg file and away you go. So naturally, when I installed DBMan SQL I looked through the documentation and immediately started searching for the section that tells you how to setup the cfg file (or the new equivalent to a cfg file). It makes no sense to me at all.

I already have a database named webapps and it contains my tables for the web applications I will be using. I don't want to create any databases or create tables or modify tables etc. I just want to configure DBMan SQL so I can start using the auto generated data entry screens with the tables I already have.

When I installed DBMan SQL I installed it in a database called "dbman." I can't figure out how to access the tables in a different database, like webapps. The install asks you for a default table. The concept of a default table doesn't make sense either. I have lots of tables I want to manage data for and they're all independent of each other. As far as I can tell there is no "default" table. I will be using DBMan to edit data in my tables, a concept similar to using a word processor to edit documents. Asking for a default table is like installing a word processor and asking for a default letter upon installation. It's going to change upon each use. I'm totally missing the boat here.

Is there a document that explains the DBMan SQL archetecture? The pdf file that comes with it does not. On chapter 3 "The Admin Panel: Tables" doesn't even tell you what URL to go to to access the admin panel. This is really frustrating.