Unfortunately, what you are seeing sounds about right. RunRev loads the whole stack into memory, and when you save it it actually backs up the old stack, saves out you changes to a new file, then, when it knows everything went well, it deletes the old file, so forty seconds is, if you think about it, really fast.
I'm guessing that this stack is a database-type-of-thing, and that you have groups that are on each card that hold all you data - right? What you might try doing is adding a text data import/export function to your stack, and exporting all the data out to a text file to keep it safe, then ceating a smaller data set to use during development. THat way you can do all your development quickly with a small test data set, then, when things are where you like it, import the data into the revised stack. Going forward, you do all your development on the development stack, and when you are happy with it, export the data from the working stack and import it into the new version. >----- ------- Original Message ------- ----- >From: Jo=?ISO-8859-1?B?6w==?=l Guillod ><[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Wed, 09 Jul 2003 18:36:49 > >I have a stack with 13752 cards and found that it >takes more than 40 secs to >save it after just having edited the script of the >stack. > >I run under MacOSX 10.2.6, G4 1Gz, 500MB RAM. Is >this duration expected or >is there something wrong? > >And do not try to open the Application Browser or a >Property palette >otherwise it takes many minutes before giving me >the hand back (of course, >it tries to load a list of all cds names...). After >5+ minutes, I canceled >it... > >Cheers, > >Joel > >_______________________________________________ >use-revolution mailing list >[EMAIL PROTECTED] >http://lists.runrev.com/mailman/listinfo/use-revolu >tion _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
