-
I apologize for misunderstanding your question. I was talking about hyperlinks, you were talking about anchors (which are a form of hyperlink). InfoPath does not support anchors. There is no good way to jump to a specific portion of the view from within InfoPath. There are methods for selecting fields or text within fields... but these are clumbsy ...
-
In the Controls task pane, insert a Hyperlink control.
-
VSTO creates the link for Visual Studio to do Office development. You just need to have it installed on the machine you will be developing on.
To create a new InfoPath template:
Launch Visual Studio.
Create a new project.
In the New Project dialog box, expand either the Visual C# or Visual Basic tree.
Select Office.
In the ...
-
Are you using rules? In a repeating table, current() will either be pointing to your row or to the field, depending on how you have things set up.
I'm not sure whether my:Repeating is the actual repeating row or the container and my:ITR is the repeating row.
You can try one of the following (assumes current() = the ...
-
Unfortunately, without a Web service, user information is a security issue. In managed code you can get the user alias without seucirty issues, and that's it. A Web service is needed if you want to get more detailed information.
-
You have to use a little trickery to do what you want to do. It involves having two sections. Inside one section you show the file attachment with the insert turned off. In the second you have it turned on. Then you use conditional formatting to show one or the other based on whether there is an existing attachment.
-
Great! I'm glad to hear that you got it working. Keep up the good work!
-
It sounds as though someone manually edited the schema file and added that restriction. I'm not aware of any place in the designer where you can create such a restriction and have it appear in the properties.
Extract your form files, edit the myschema.xsd file in notepad and see if there's a limit added to that attribute in there.
-
No. Namespace definitions don't chnage just because you make schema changes. This kind of change happens when you do something more significant... like "swap out" the schema, or create a new form template based on an old one. Just adding/renaming/removing schema elements/attributes will not change your namespace definition.
-
Perhaps your form schema has a character restriction on it? Did you create the schema in InfoPath or outside of it?