Hi Mark,
Couldn't agree more.
I name my stacks stkName, stkOthernMe cards are crdName etc fields used
for lists are lstName - Got used to that using foxpro.
One way out of this is without having to rewrite everything, is rename the
stacks with stkRev (for instance) and wherever there is a display of the
name needed instead of "display" "StkName"
it displays FixName("stkName") where fixname returns the stack name without
the "stk" prefix
Lagi
On Fri, 28 Sep 2018 at 00:13, Mark Wieder via use-livecode <
use-livecode@lists.runrev.com> wrote:
> On 09/27/2018 03:47 PM, J. Landman Gay via use-livecode 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
> ahsoftw...@gmail.com
>
> _______________________________________________
> 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
>
_______________________________________________
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
