Many thanks to all. As usual, your insights are very helpful and welcome. -- Douglas von Roeder 949-336-2902
On Thu, Nov 17, 2016 at 9:50 AM, Arnaud de Montard <[email protected]> wrote: > > > Le 15 nov. 2016 à 22:06, Kirk Brooks <[email protected]> a écrit : > > > > Doug, > > This option is so appealing - storing large data chunks outside of the > > actual data file. I tried it briefly in v13 something as well. I > abandoned > > it for two reasons. First, there's no option to exclude these files from > > the backup. Second I wasn't confident about maintaining the links to the > > external files within 4D if something got moved externally. > > third reason: > [artwork] > name > author > description > photo (external storage) > LOAD RECORD([artwork]) //photo is loaded too :-( > > Another (bad?) reason is that it took me a while to understand the way 4D > organizes the folders. > > I prefer doing it myself. > [artwork] > name > author > description > photo_ID > The path is made from photo_ID. > > If I plan to move documents one day "somewhere else" (cloud or something), > things will be easier I suppose. > > -- > Arnaud > > > ********************************************************************** > 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] **********************************************************************
