-
You can attach files to messages in this forum by clicking the Options tag when creating a message.
Please try this code: XPathNodeIterator xp = xnMyForm.Select("/dfs:myFields/dfs:dataFields/tns:GetRequesterResponse/tns:GetRequesterResult/tns:string", NamespaceManager);
while (xp.MoveNext())
{
...
-
The Insert command in Qdabra's qRules is capable of doing this. Please give that a try and let us know if it does the trick.
-
This is entirely possible in InfoPath, but you need to put the data in a format that InfoPath will understand. This is a little tricky when the original data is in Excel. I created and ran an XSL transform on the data in your spreadsheet to produce the attached XML file. This can then be added as a secondary data source in ...
-
Why can't you post a screenshot of your data source? I don't really understand which node is the repeating one from the way you described it.
The correct approach here is to use xp.Current and relative XPaths, not to concatenate an index value into an absolute path. If you could post a screenshot of your data source or ...
-
Have you tried right-clicking the file in Windows Explorer and clicking Design?
-
You need to set values for your three parameters. Please have a look at this:
http://www.csharp-station.com/Tutorials/AdoDotNet/lesson06.aspx
That tutorial adds parameters like this:SqlParameter param = new SqlParameter();
param.ParameterName = "@City";
param.Value = inputCity;
cmd.Parameters.Add(param);But ...
-
That's Visual Basic code, not C#. Please change the form's programming language to C# in Tools->Form Options->Programming, and add your C# code again.
-
The code you've posted looks fine the way it is. Is there possibly some other code you're not showing us?
Could you also make sure that your form is set to use C# code and not Visual Basic?
-
You're certainly right. This is due to small roundoff errors in floating point arithmetic causing 150.98 * 100 to produce 15097.9999999998 instead of 15098. This should solve the problem:
Changevar hundredths = parseInt((num * 100 - parseInt(num) * 100));
to var hundredths = Math.floor(num * 100 + 0.1) - ...
-
http://msdn.microsoft.com/en-us/library/aa947462%28VS.80%29.aspx
http://msdn.microsoft.com/en-us/library/ms757878%28VS.85%29.aspx
There is no straightforward way to determine whether a section is hidden or not. Sections are hidden based on your own conditional logic, so you would have to evaluate the same logic in your code to ...