Copying many cds to a stack causes standalone to hang

Steve Denney steve.denney at bigpond.com
Mon Nov 27 15:58:23 CST 2006


Hi PL,
The app is a catalogue where users can view pics of the products & click on
them to order (amongst other things). 
Currently each product page (card) is kept in a single cd stack file and all
the pages are copied into one stack at start up. I've now realized it'll be
better to have collections of product pages (by brand) in fewer stacks with
many cards.
I also thought cross brand searching and movement between cds would be made
easier by having all the cards present in the one open stack. Now I'm
considering keeping each brand collection in its own stack (i.e. no copying
of cds - not that I'm not immensely grateful for the effort everyone's put
in and finding out the true nature of the 'start using' command :) And
opening and searching each 'brand' stack only as required. 
My feeling is the latter will work just as well (without waiting for
"Loading catalogues..." on openStack), or (as you point out) having to deal
with a huge unwieldy stack, especially if I don't bother to encrypt the
catalogue pages.
All comments and suggestion most welcome.
Thanks again everyone.
Steve Denney

-----Original Message-----
From: use-revolution-bounces at lists.runrev.com
[mailto:use-revolution-bounces at lists.runrev.com] On Behalf Of
simplsol at aol.com
Sent: Tuesday, 28 November 2006 2:22 AM
To: use-revolution at lists.runrev.com
Subject: Re: Copying many cds to a stack causes standalone to hang

Steve,
I don't know if this has been mentioned:
Rev opens, manipulates, and saves stacks with a lot of cards slowly.
We were updating one large stack that seemed to hang each time. It was 
a stack imported from HyperCard where the same update took about half 
an hour. The update consisted of pulling data from the old stack, card 
by card and field by field, and putting it into a new stack, card by 
card and field by field. Fortunately we were able to just let the 
update run overnight on a surplus computer. In Rev the update worked, 
it just took over 20 hours. Until it we were able to let it finish we 
always figured Rev had simply hung.
Storing you data in a database with a single card front end, already 
suggested by others, will give you much more speed than storing it as 
cards in a stack.
PL



________________________________________________________________________
Check out the new AOL.  Most comprehensive set of free safety and 
security tools, free access to millions of high-quality videos from 
across the web, free AOL Mail and more.

_______________________________________________
use-revolution mailing list
use-revolution at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution




More information about the use-livecode mailing list