Great article... but maybe I read it wrong -- I took from the article that FOR XML EXPLICIT is SQL 2005 only, when you could do the same in SQL...

Good article, but just one suggestion. The title is "Introduction to Bitmasking in SQL Server 2005" but the same code you have given will work just fine in SQL Server...

You should set any object you user to nothing after you're done with them. If not you may create a memory hungry app and start having random bugs/issues in your...

After you persist your recordset to xml:

             RS.Save "myRS.xml", adPersistXML

You can then load that xml file into a DomDocument and re-open it in another recordset:

             Set oXml = Server.CreateObject("MSXML2.DomDocument.4")

             Set...

quote:

---

Hi Frank,

Yes, laziness on my part. If you leave off 'Server.' it is assumed (bad practice ).

I know ASSuME...