InfoPath Dev

To update a control field one of the articels uses the following code:

strStartDate = XDocument.DOM.selectSingleNode _

("/my:myFields/my:startDate").text

I am trying to use the same syntax to populate a text field in my form:

XDocument.DOM.selectSingleNode("/my:myFields/my:dataFields/d:Table1/d:Table1Item3").text = "abc"

However, The following error occurred:

Object required: 'XDocument.DOM.selectSingleNode(...)'
File:script.vbs
Line:23

My form is connected to database with two tables - namely "Table1" as the Primary and the other one "Table2".

any help please.

The select is failing, thus the .text property not valid.

Sounds like the issue is likely with the namespaces. Assuming the node names are all accurate, check to make sure each node has the appropraite namespace. For example, "my:" on dataFields looks suspicious to me.

The node names are as in the Data source. I think you are right the issue may be with the namespaces because i have no clue how they work. is there a quick tutorial i can get my hands on.

This is what my Data source looks like if that is of any help. (For some reaon i am unable to upload its image file hence this representattion below).

Table1 is the primary table with three elemenst namely Table1Item1, Table1Item2 and Table1Item3. Table2 is another table with 3 elements too.

-----------------------------------------------------------

- myFields

  + queryFields

  - datFields

    - d:Table1

        Table1Item1

        Table1Item2

        Table1Item3

    - Table2

         Table2Item1

         Table2Item2

i have my answer:

XDocument.DOM.selectSingleNode("//dfs:myFields/dfs:dataFields/d:Table1/@Table1Item3").text = "abc"

though dont ahve a clue why "dfs" and not "my" and "@". Any tutorial i can read to understand these?

The '@' (typically pronounced 'at') symbol is used to differentiate an 'at'tribute from an element. So 'Item' is an element, while '@item' is an attribute.

Namespaces help keep names distinct and different. For example, there are lots of people in the world named Greg, but there are not as many named Greg Collins... so in this human name example, my personal namespace could be my surname and I could be represented as collins:greg to differentiate me from jones:greg or smith:greg. If someone called out for smith:greg, I would have no reason to answer. Make sense?

InfoPath uses the 'my' namespace for everything, but a data source has a few different namespaces they use, as you see in your example 'dfs', 'd' and no namespace at all in the case of the attribute.