Q. data stacks and app design

[Sarah]

If you are going to be reading your saved data from another stack, the 
easiest thing is probably to save a copy of the data stack somewhere. 
Then your reader stack can just open the saved data stack at any stage. 
When you build your app, make sure it saves the substacks into separate 
files. This will allow your data stack to be saved (so long as it isn't 
the mainStack) either to it's default location or to your storage 
location.

Sarah

On Friday, October 4, 2002, at 10:55  am, Alex Rice wrote:

> I am writing an app which is a long survey followed by a couple of 
> long reports. I want to save the state of the survey to disk and have 
> different projects which the user names/saves/restores. Each project 
> is just the set of answers to the survey questions.
>
> A SQL database is not needed. In the SQL mindset, this data would have 
> a handful of rows and maybe too many columns to deal with-- many 
> hundreds. I'm sure it could be normalized better, but there is not 
> enough data to warrant a SQL database.
>
> Even the Serendipity Library SDB database looks like overkill for this 
> app.
>
> So I think I need to use a data stack. What's the most elegant way to 
> get cards and/or stacks to write all it's state out to disk, which I 
> can go check on later from another stack, and write a report from the 
> responses? I hope this question isn't too vague. I'd be glad to tell 
> more about the application if it's not clear what I'm asking.
>
> Thanks in advance!
>
> Alex Rice, Software Developer
> Architectural Research Consultants, Inc.
> alrice at swcp.com
> alex_rice at arc.to
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>