OK. So are you also having to implement the database itself? Does that give you control over the RDBMS you use on the backend?

If you get to design the database, you get to make things possible. If you are handed a database to query against, then you can discover the list of tables, hopefully programmaticly. One can hope that the relationships can also be discovered on the fly.

yours,
Michael

Hi,

I really don't know what they did. Anyway, you get the whole system which displays all there is in the database in a way that is attractive. So if you already have any database that is for example a catalog, a list of departments, workers and projects and etc., or any other database of something that have to be displayed in arranged way, you'll get this without doing any of the work yourself. And you can apply it to any database and DBMS. I know, this sounds like a miracle, but they somehow did it, at least that is what they claim.

Howdy!

OK. They have to be betting on getting the top-level item from the user at installation time and then reading the catalog/metadata to drill down to get all the elements. That implies that the RDBMS used to implement the database must necessarily support the use of that metadata.

Given their claim, then I would say that it can be done with Perl and DBI.

yours,
Michael