-
You may want to check if you have any styles applied - sometimes those seem to render differently in the browser.
Or you might want to try copying your controls into a new view - I know of one forum poster who recently had a view displaying incorrectly in IPFS, and copying his layout table and contents into a new view fixed the issue for him.
-
What is the rule you have on your field that is setting the other field? Or default value, if that is what you are using instead? When you look at the value in the formula editor, check the edit XPath button and paste the full XPath into a reply - I'm going to bet your formula is not using current()....
-
I'm attaching a simple sample form with some calculated values that may help you. Save the file locally. Right click on the saved XSN and select Design to open in design mode. From there you can preview to try the form.
-
How odd. I guess at this point I'd probably try repairing InfoPath.
-
You can't actually type there - but here's a blog post that tells you how to do this by manually modifying the source files.
-
Well, you'd said:
70 milestones, each milestone can have upwards of 10 tasks with a status, completed by and completed time respectively
So, to me, based on that description, I would assume the schema would look somthing like the attached screenshot. If you need 70 instances by default, you can set that up in the form's default ...
-
If the data type on the field is set to Date, they will get a validation error.
-
Well, yes, the larger the view, the slower the form.
I'm wondering why you haven't chosen a repeating structure for the data source?
-
I'm going to bet it depends on whether the template is saved as IP 2010 or IP 2007....
-
Are you talking about in your form schema? You could just add a reference to your existing group.... That creates a new instance of the group, but with the same schema. Right click the group in the data source task pane, and select Reference. Then select the other group where you want the same fields.