-
I believe there is. I'm not sure what the various limits are.
I suspect there is an overall limit to the total number of promoted fields. But I do know that there are limits to the number of fields of a particular type... i.e. you can only promote X integer fields, Y date fields, and Z string fields.
Again, I'm not sure what those limits are, ...
-
As the results will likely be returned as a repeating set of data, then a repeating table or repeating section is the right choice of controls to display the results.
-
The code I wrote was just a skeleton of your onafterchange event. It was demonstrating the use of a flag to prevent endless loops: i.e. the onafterchange event handler causing another call to the same hanlder, and so on...
You will need to write your own code to do accomplish what you want inside the handler.
-
Yes, this works for both 2003 and 2007. I am currently using it to design 2003 managed code forms.
-
public void SomeField_OnAfterChange(...)
{
if(e.UndoRedo || e.Operation != ''Insert'' || fIsUpdatingFields == true)
return;
fIsUpdatingFields = true;
// Modify DOM here.
fIsUpdatingFields = false;
}
-
SE also works with 2003, although you have to do some digging through their online text to discover this.
-
You should be able to do this--no different than you would on an ASPX page.
However, you might find that your form needs to be full trust in this case, though I don't know for sure.
-
InfoPath sandboxes such events, so you won't be able to do this by normal means...
You will need to have a custom ActiveX control to handle this.
-
Sounds like you have the same old problem of your OnAfterChange event handler updating someting which causes the handler to get called again.
The easiest way to prevent this is to set a global flag (variable) which states that your OAC event handler is making DOM changes. Then at the top of your handler, if that flag is set to true, return out ...
-
The best way to accomplish what you want is to sort the list by code once its been loaded into InfoPath. Web based forms should support managed code, so you should be able to do this with C# or VB.NET.
Sort by both columns: first drop-down, then second drop-down:
A A
A B
A C
B A
B B
B C
C A
C B
C C
Then it doesn't matter what sorting the SP ...