Fran�ois Cuneo wrote (rearranged in standard reading order for clarity): >> I have a handler that reads selected data from all stacks in a >> folder--1,648 in my real-world situation >> >> As it finishes processing a stack, my export handler does: >> >> set the destroyStack of stack currentStackName to true >> close stack currentStackName >> >> This seems to be working fine for moi...am I missing somethng? >> > Until here OK, it works too, but if I refer again to another stack after, > it's impossible without a warning message "...what to do with the stack > XXX".
Have you tried saving the destroyStack property for each stack? You'll only need to do that once, and then the stack will never be confused with that's supposed to stay resident -- and it cuts out one line of code. :) -- Richard Gaskin Fourth World Media Corporation Developer of WebMerge: Publish any database on any Web site ___________________________________________________________ [EMAIL PROTECTED] http://www.FourthWorld.com Tel: 323-225-3717 AIM: FourthWorldInc _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
