I think you're on to something there Chuck! We would still need to have all those tables but any that are not being used only have 1 field instead of over 500! Why didn't I think of that?
Pat On Wed, 8 Mar 2017 at 00:27, Chuck Miller via 4D_Tech <4d_tech@lists.4d.com> wrote: > Yu could simply create tables with only journal field and allow users to > adjust as need be. Set triggers to run as needed and uses footprints to run > trigger method. I know this last part is not pretty but it may work > > Regards > > Chuck > > ------------------------------------------------------------------------------------------------ > Chuck Miller Voice: (617) 739-0306 > Informed Solutions, Inc. Fax: (617) 232-1064 > mailto:cjmiller<AT SIGN>informed-solutions.com > Brookline, MA 02446 USA Registered 4D Developer > Providers of 4D and Sybase connectivity > http://www.informed-solutions.com > > ------------------------------------------------------------------------------------------------ > This message and any attached documents contain information which may be > confidential, subject to privilege or exempt from disclosure under > applicable law. These materials are intended only for the use of the > intended recipient. If you are not the intended recipient of this > transmission, you are hereby notified that any distribution, disclosure, > printing, copying, storage, modification or the taking of any action in > reliance upon this transmission is strictly prohibited. Delivery of this > message to any person other than the intended recipient shall not > compromise or waive such confidentiality, privilege or exemption from > disclosure as to this communication. > > > On Mar 7, 2017, at 6:15 PM, Pat Bensky via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > > > 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 > > ********************************************************************** > 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:4d_tech-unsubscr...@lists.4d.com > ********************************************************************** -- ************************************************* CatBase - The Database Publishing Solution tel: +44 (0) 207 118 7889 w: http://www.catbase.com skype: pat.bensky ************************************************* ********************************************************************** 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:4d_tech-unsubscr...@lists.4d.com **********************************************************************
