-
There is no programmatic way to do this.
To get filters to automatically apply, remove useFilter and refreshFilter attributes from manifest.xsf file. This might cause other issues when inserting rows unless you make sure that the filter criteria is available on the new row.
-
See my reply to your other post. Please don't double-post the same question. Thanks.
-
You don't access the control. This is never allowed.
Create a secondary data source with a boolean field. Your code sets the field. Conditional formatting sets the control to readonly based on that field.
-
It is always best to have full email addresses anyway. Even corporate email can have issues with just aliases.
-
Is it supplying a full email address (i.e. user@domain.com) or just a user alias (i.e. user)? Makes a difference. The user alias can be used on corporate domains where the email system auto-resolves them, but outside of that, you will probably need to have full email addresses so there's no resolving issues.
-
Great! Glad to be able to help out!
-
If your drop-down is manually populated (i.e. in the control itself), then you just set the field default value to the first drop-down value. Then you have to manually edit your XSL to get rid of the blank option.
If your drop-down is populated from another data source, then you can probably write an open rule to populate the bound field with the ...
-
When you set up your conditional formatting, you will be pointing to a field in the repeating table and checking a condition.
So for example, you might have conditional formatting that says where [field1] [is not equal to] ["abc"]
This kind of formatting will only get the first row field1.
In the Select A Field Or Group dialog box, ...
-
The problem is your select code. Your absolute XPath is saying to go back to the root node, then find the field.... If you follow the logic of your XPath, you will see that it will of course always select the first row. It has no other choice.
The trick here is that eventObj.Source points to the row that the button is located on. So you only need ...
-
I don't necessarily have an answer to you question -- however, the DLL is part of the XSN, so that shouldn't be the issue.
You probably already have this covered -- but I just want to mention that web based forms will not work in SharePoint 2003.
Hopefully someone else has more info for you that this...