Pat,
how about :
1 table - each record contains an object field which holds a table definition,
which the user can define.
1 more table - each record has an object field which holds the data for the
table defined above
> I'm revisiting the idea of creating a flexible table structure with v16.
> Currently we have lots of user data tables defined, and they are
> activated/deactivated as required by each customer. This works OK but it
> adds a lot of overhead to the database, as it means we have more than 50
> tables, each with over 500 fields of various types. It would be much better
> to be able to define tables on the fly.
>
> The first obstacle is triggers. We can create a new table using the SQL
> CREATE TABLE command, but I can't see a way to programmatically add a
> trigger to it. Triggers can be enabled or disabled via the ALTER TABLE
> command, but how can a trigger be created? Is there ANY way to create a
> trigger?
>
> Thanks!
> Pat
------------
Hell is other people
Jean-Paul Sartre
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ: http://lists.4d.com/faqnug.html
Archive: http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:[email protected]
**********************************************************************
