Why create stacks when LiveCode Server can manage data via text files or databases - the orthodox data storage options for multi-user server environments, which come complete with robust security models?
If the data is structured and suits a database approach, the inherent data storage aspects of stack, cards, fields, variables and custom properties (including arrays) can be mapped onto a data-set in a database (tables, records, fields, rows). If databases are to be avoided - or if the data doesn't suit a database architecture - the LiveCode application structure can be mapped to a file-based storage model instead (folders, files, lines, line-items). Best, Keith.. On 7 Aug 2011, at 14:15, Martin Koob wrote: > I have added an enhancement request to the QCC to have 'save stack' > implemented on LiveCode Server, Report #9664 > > Is there another way to save a stack that I am missing? > > Is there a reason why allowing LiveCode server to save stacks would not be a > good idea? > > I see it could be a way to store data without having to use a database. > Poking around with stacks in LiveCode server has reminded me of starting out > with Hypercard and realizing how it could be used to store and categorize > information using stacks, substacks and cards. However if you can't save > the stacks you have to store the data in a database and each time a page > is loaded recreate the set of stacks and cards. > > > > -- > View this message in context: > http://runtime-revolution.278305.n4.nabble.com/Server-create-stack-trouble-tp3721781p3724846.html > Sent from the Revolution - User mailing list archive at Nabble.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