Thanks, I also found that out belatedly. Could you kindly read my reply to Viv esp. the part regarding XSL and the kind of XML that I am to tackle, which is not record based but is a lot of seperate types of records (tags), like styles and contents all in one file one following the other. Question is how can a single XSL file address all these varied types at one go using your sample code? What kind of a layout will this XSL file be?

The question you have asked is pretty broad in its scope and, I do not wish to be unkind, but I do not have all day to devote to teaching you everything you need to know about working with XML and XSLT.

I can tell you from experience that this is not something that you are going to learn through osmosis or by asking a couple of questions on the UT. It is a huge subject and you are going to have to do some research on your own.

I wrote the Chapter on XML in MegaFox: 1002 Things You Wanted to Know About Extending VFP. At the time I had some limited experience writing XML formatting objects for middle tier components that dished data for a couple of web sites. It was one of the hardest things I had to do because there was so much information available and some of sources said things that did not agreee with the others. I pulled information from my Professional XML and XSLT books (Wrox Press - and very good references - each of them over 700 pages in length). There is also a wealth of information available in MSDN and the MSXML SDK.

If you have a question about something more specific, I would be happy to try to answer it (provided that I know the answer < s > - I am by no means an expert on XML and XSLT )