Hi Nigel, Yeah I did look into that option as well, but it doesn't solve the trigger problem. Triggers are essential to us! Pat
On 8 March 2017 at 12:19, Nigel Greenlee via 4D_Tech <[email protected]> wrote: > Pat > > A sideways question for your concept. > > 1) Are you creating the tables in the main structure or using the external > datafile( CREATE DATABASE IF NOT EXISTS DATAFILE > <<$_t_CustomTablesPath>>;) .(I use an external datafile structure for some > things-very useful..it could be useful in your scenario as the created > tables and data could remain intact with new builds. > > > I have not tested to see if you can set the trigger code on a table in an > external data file and if you can do it compiled..the external datafile is > not compiled..but i suspect the answer is no! > > I guess the other option is to go back to the days before we had triggers > and set a process to look for modified records in the created tables… > > Nigel Greenlee > > > > > > > > On 8 Mar 2017, at 10:10, Pat Bensky via 4D_Tech <[email protected]> > wrote: > > > > Hi Arnaud, > > Yes, but the thing is that the TABLES will not be missing, only the > custom > > fields that the client created. Now if there was a REGENERATE MISSING > > FIELDS function ... > > > > On 8 March 2017 at 09:59, Arnaud de Montard via 4D_Tech < > > [email protected]> wrote: > > > >> > >>> Le 8 mars 2017 à 10:19, Pat Bensky via 4D_Tech <[email protected]> > a > >> écrit : > >>> > >>> [...] Also I've realised that there is another fundamental problem with > >> the idea > >>> of allowing customers to create new fields: when we issue a program > >> update, > >>> those custom fields - and their data - will be lost! > >> > >> See GET MISSING TABLE NAMES and REGENERATE MISSING TABLE: > >> <http://doc.4d.com/4Dv16/4D/16/GET-MISSING-TABLE-NAMES. > 301-3036706.en.html > >>> > >> > >> -- > >> Arnaud de Montard > >> > >> > >> > >> > >> ********************************************************************** > >> 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] > >> ********************************************************************** > >> > > > > > > > > -- > > ************************************************* > > 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:[email protected] > > ********************************************************************** > > ********************************************************************** > 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] > ********************************************************************** > -- ************************************************* 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:[email protected] **********************************************************************
