Hmmm... If she means that she has links or buttons that navigate to various stacks and cards, I'm not sure how else she could do it. I suppose setting properties or constants in scripts might work. But you cannot get around the fact that when navigating to what amounts to a form, it needs to be a hard reference somehow.
Bob S > On Sep 27, 2018, at 16:12 , Mark Wieder via use-livecode > <use-livecode@lists.runrev.com> wrote: > >> The reason the stack name can't be changed is because the whole multi-stack >> system uses the stack name for internal display in dozens of places >> (glossaries, gradebooks, student notes, reading history, lookups, > > Really really really a bad idea. > I'm sure you knew that already, but I want to say it again. > That's really really really a bad idea. > > One of the prime tenets of database design is that you shouldn't use actual > data to link items together. Else you get into maintenance nightmares and > things fall apart when you get unexpected data, etc. > > I hate to say you should rethink the design, but you should probably rethink > the design. > > -- > Mark Wieder _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
