error code 3265 Item cannot be found in the collection ... Why is this happening

Help!

Vb new boy has written a small application interfacing with a sqlserver database.

need to take data that has been added to database and output it as an xml file in order that it can be accessed by another application.

I was given the code below and told it should work - can't see why it shouldn't but then...

The application falls over at the oCmd.Properties("Output Stream") = oDom statement - error code 3265 Item cannot be found in the collection corresponding to the requested name or ordinal. I have no idea what this means.

Should the "Output Stream" statement read something other than "Output Stream"? If so, what?

Can anybody shed any light for me and tell me how to remedy the problem?

Thank you in advance

     'Instance of XML Parser
    Dim oCmd, sSQL, oDom

    ''' If MSXML 4.0 is not installed this will not work!
    Set oDom = CreateObject("Msxml2.DOMDocument.4.0")

    Set oCmd = CreateObject("ADODB.Command")
    oCmd.ActiveConnection = "Provider=SQLOLEDB;Data Source=(local);Initial Catalog=SCLAnodising;UID=GCroxford;Password=xxxxx"

    sSQL = "<ROOT xmlns:sql="urn:schemas-microsoft-com:xml-sql"><sql:query>" & "select * from Build_Validation for xml auto</sql:query></ROOT>"

    oCmd.CommandText = sSQL

    oCmd.Dialect = "{5D531CB2-E6Ed-11D2-B252-00C04F681B71}"

    oCmd.Properties("Output Stream") = oDom
    oCmd.Execute , , 1024

    oDom.Save "C:\Documents and Settings\Desktop\testdts.xml"
ReneLMadsenAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

cubixSoftwareCommented:
Hi

Usually this means that either the property "Properties" or "Output Stream" does not exist for the object you are using which in this case is the ADODB.Command object.

A better way would be to use the intelliense so try the following...

dim oCmd as new Adodb.Command


then delete the statement where you Set oCmd = CreateObject....

then within the editor, if you type oCmd.  you should then get a list of all the properties available (make sure you do the .) and you can check if Properties exists.

Below is a link to microsoft KB to give a working example

http://support.microsoft.com/kb/q271620/

HTH :)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.