-
I think for the sections where you are seeing large blocks of white space, InfoPath has changed the section height from Auto, or if they are in a layout table row, that has been set to a specific height rather than Auto - start checking the properties of the sections, layout table rows, etc for the affected areas.
-
You bet, glad you have it working!
-
Here's the issue - rows is at my:Images, so you need relative XPath for the rest:
while (rows.MoveNext())
{
string s = rows.Current.SelectSingleNode("my:InkImage", NamespaceManager).Value;
Image drawnImage = Base64ToImage(s);
Image resizedImage = ResizeImage(drawnImage, new Size(100, 100));
s = ImageToBase64(resizedImage, ...
-
Your syntax is off. In your formula, you need a "/" before the word XPath.
-
First, if you are using a concat statement, you must use the function builder.You'd pick txtFilter and txtValue using the field picker, most likely. Your formula above looks correct. Whe you say "I get the same result" what does that mean? Are you able to save your function? Any information in the Qdabra Rules error node?
-
This is correct. InfoPath Forms Services is only included with the Enterprise version of MOSS.
-
Let's say my:Images is your repeating node - I figure that would be a good guess....
You'd want to create an XPathNodeIterator pointing to your repeating my:Images, and then loop through them, using relative paths from there "my:InkImage", "my:ShrunkenImage", etc. Here's an MSDN page with a code sample that should ...
-
Well, just to be annoyingly specific, a repeating table and a repeating section are just controls - the underlying data structure (which is a repeating group) is the same. Now, if you want to sum a field like TotalOP, you can put an expression box inside a section bound to group1 and use the formula sum(POP_TotalOP), selecting the field using the ...
-
Sometimes it seems the act of asking the question helps us find the answer on our own... Thanks for updating with your resolution.
-
And you've tried publishing to a new library as well? Just in case? Do you get any additional info about why the form won't be accessible in the browser now that you are publishing a form you have the source code to?