> >Create a new XmlElemNew and use the ArrayInsertAt to insert a new > XmlChildren > >item. > > > You're glossing over quite a lot with that statement.
That is true - there is alot inside that, but I feel most of it is relatively straight forward (and feel free to disagree there) > > If you want to put a product in the new node, and the product itself > contains a bunch of nested sub-nodes, the code to manaually generate > the > new node really does start to look a bit ugly when compared to > inserting > similarly complex data into a database. Oh yeah - I'm not going to say that putting stuff in the database is harder than putting it into a text file! Woah no... I wouldn't be replacing my DBs with XML files... ;o) Just saying that managing a XML file is not THAT hard. It's not something that I'd be running on a regular basis - but maybe more as part of an admin console etc. And just like anything else - you need to be careful where you put things, otherwise they end up in the wrong place. Again - all depends. Mark ----------------------------------- [EMAIL PROTECTED] ICQ: 3094740 Safe From Bees [www.safefrombees.com] --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MX Downunder AsiaPac DevCon - http://mxdu.com/
