> Le 26 janv. 2018 à 18:49, Kirk Brooks via 4D_Tech <[email protected]> a > écrit : > > Arnaud, > On Fri, Jan 26, 2018 at 7:34 AM, Arnaud de Montard via 4D_Tech < > [email protected]> wrote: >> >> Some field options would make it better: >> • don't load with record (something like a command 'External field load') >> > My understanding is this is the way it works already. > Have you seen otherwise?
Things may have changed, but last time I tried, LOAD RECORD would grab the whole stuff (and I suppose it could be considered as a bug if not). I store photographs, for example, in 3 different resolutions, that external storage will only reduce my 4dd size, nothing else. With my own external storage I don't have this problem. >> • exclude from backup (very easy IMHO) >> > I thought about this too and concluded it's probably not a good idea. The > reason being it creates two 'classes' of data and that's not good. Yes, perfectly true. But it's exactly the same if I create create my own "home made" external storage, and I don't ask 4D to care about it. Makes me think of the backup file: I never understood why a 4D backup must be a file instead of a folder containing what I need to restart immediately (4dd, 4dindx, etc). No, I have to _extract_ the monster first. Sometimes I wonder if they know we are adults. -- 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] **********************************************************************
