>> Doesn't storing them in an array create a set of references that will need to be cleaned up?
Absolutely (if the app performance even needs cleaning up and/or the items are even removed). But that's easily taken care of with a cleanup function. So for small uses, as I mentioned, may not be worthwhile, but I am thinking long term scalability. I just hate to see people default to dynamic naming all the time when architecturally, using arrays as storage is better in the long run. For this, the dynamic naming would be fine. I'd just be careful to make it a habit for everything. Jason Merrill Bank of America Global Learning Learning & Performance Solutions Join the Bank of America Flash Platform Community and visit our Instructional Technology Design Blog (note: these are for Bank of America employees only) _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
