The Flash Movie also may become slow or unstable with a large consumption of
memory or large loops which usually occurs with XML parsing.

Look at breaking the XML into multiple smaller files and loading them on
demand with the user. Perhaps one XML file for every product or product
group (not sure how your data is organized but some data analysis work is
probably in order).

Look at creating smaller index XML files that you could load for common
search criteria.

--
Lon Hosford
www.lonhosford.com
May many happy bits flow your way!
[quoted text, click to view]
Hi Friend

I have got a small query for you, Basically we are making a Flash Based
CD
rom presentation which even includes product catalog. This product catalog
has
Category=> Sub Category then the product i know a way how to do this using
access as a database and then query it and work with it.

But i want to know what if i create a similar data structre in XML will it
be
reliable and faster then access please help me with your advice. Coz i read
somewhere that flash first loads the enite xml file and then it works. So in
my
case i have 60,000 records which means the p[resentation will stop working
coz
of this chunk of datya being loaded.

Please Help

Regards

Hi Friend

I have got a small query for you, Basically we are making a Flash Based CD
rom presentation which even includes product catalog. This product catalog has
Category=> Sub Category then the product i know a way how to do this using
access as a database and then query it and work with it.

But i want to know what if i create a similar data structre in XML will it be
reliable and faster then access please help me with your advice. Coz i read
somewhere that flash first loads the enite xml file and then it works. So in my
case i have 60,000 records which means the p[resentation will stop working coz
of this chunk of datya being loaded.

Please Help

Regards