InfoPath 2007

  1. The specified form template could not be migrated. The feature name {0} that was specified is the wrong format. You can migrate ...
  2. The specified location does not exist or could not be opened. Choose a data connection library on a server running Microsoft ...
  3. The specified location is not a data connection library. Choose a data connection library on a server running Microsoft Office ...
  4. The specified location is not valid, not available, or you do not have the correct permissions. Check the spelling of the ...
  5. The specified query did not return any data. You can revise the query, or you can click New Record to enter a new record. ...
  6. The specified save location '{0}' is not valid. Use an absolute URL to the desired file location, or specify only the file ...
  7. The specified task pane cannot be displayed. Either the task pane cannot be displayed when the form is open in the current ...
  8. The specified URL cannot be used. This error could be caused by any of the following: the URL is not valid or uses a relative ...
  9. The specified varNode value and varViewContext value for the View.GetContextNodes call is not in the view or is in the view ...
  10. The specified XML template file (xsf:initialXmlDocument element) contains a urn reference that does not match the solutions ...
  11. The SQL statement cannot be represented as a tree view. To remove the SQL statement, click Edit SQL, and then delete the ...
  12. The structure of the selected .xml file will provide the data source for your form template. Do you also want to use the ...
  13. The submit operation for the Web service requires the following parameters. Specify which fields or groups in your form provide ...
  14. The submit operation for the Web service requires the parameters listed below. You can specify which elements in your form ...
  15. The submit section (xsf:submit element) in the form definition (.xsf) file is missing the href attribute, or the attribute ...
  16. The submit section (xsf:submit element) in the form definition (.xsf) file is missing the method attribute or the attribute ...
  17. The submit section (xsf:submit element) in the form definition (.xsf) file specifies the following HTTP method, which is ...
  18. The submit section in the form definition (.xsf) file contains the following error: Attribute: %1!s! Invalid value:%2!s! ...
  19. The time entered is not allowed. Verify that the time is entered according to a 24-hour clock and in 15 minute increments ...
  20. The update cannot be completed, because you do not have permission to modify the location where the template is installed. ...
  21. The updated form template is identified by the following URN: %1!s!. The original form template at this location was identified ...
  22. The URL specifies that the form should open in Microsoft Office InfoPath, but the required version is not currently installed. ...
  23. The URL {0} is an unsupported relative URL. Use an absolute URL or prefix with '~sitecollection', for a site-collection-relative ...
  24. The value of an ID key or timestamp has been changed. ID keys and timestamp columns are automatically generated by the data ...
  25. The value of the DefaultDataConnectionTimeout property must not be greater than that of the MaxDataConnectionTimeout property. ...
  26. The value specified for the destination host (%1) is not valid. The value specified must be either a UNC path that includes ...
  27. The version specified in the form template has the wrong format. To fix the format in design mode, click Form Options on ...
  28. The view %1!s! cannot be updated. Modify the xsf:view entry in the form definition file (.xsf) to include design-mode="protected" ...
  29. The view (.xsl) file contains customized ID attributes. Because |9 automatically generates ID attributes in .xsl files, this ...
  30. The view (.xsl) file creates an HTML file which includes a tag, which is not allowed. This can happen if the .xsl file has ...
  31. The view (.xsl) file creates an HTML file with an invalid tag, which is not allowed. This can happen if the .xsl file has ...
  32. The view (.xsl) file creates an HTML file with more than one tag, which is not allowed. This can happen if the .xsl file ...
  33. The view (.xsl) file creates an HTML file with nested tags, which is not allowed. This can happen if the .xsl file has been ...
  34. The view cannot be refreshed, because the form template was removed from your computer. To fix this problem, make sure that ...
  35. The view contains an xd:binding attribute that is not valid. The xd:binding attribute cannot be bound by default to a CODE ...
  36. The view contains nested formatting which is not supported on InfoPath Forms Services. Examples of such formatting include ...
  37. The Web service for verifying browser compatibility of the form template could not execute because the specified URL ({0}) ...
  38. The Windows SharePoint Services server at %1 does not fully support Microsoft Office InfoPath. Document library features ...
  39. The word cannot be added to the custom dictionary because no custom dictionary can be found or the custom dictionary is full. ...
  40. The XML data returned from the data source does not match the XML Schema for this form. This discrepancy might be caused ...
  41. The XML file %1 referenced a schema that was missing or invalid. InfoPath will generate a new schema for this form template. ...
  42. The XML Schema contains one or more elements with a complexType that references an optional element more than once. This ...
  43. The XML Schema contains whitespace characters in the following namespace declaration: %1!s! InfoPath does not support namespaces ...
  44. The XML Schema or XML document cannot be used because InfoPath does not support adding complete XML Schemas without a target ...
  45. The XML Schema you selected cannot be added because it contains structures that InfoPath cannot completely support without ...
  46. The XML template file (specified in the xsf:initialXmlDocument element of the form template definition file) has a processing ...
  47. The XmlFormView Control cannot be loaded because the AspCompat property of the aspx page is set to true. XmlFormView is not ...
  48. The XPath function used to retrieve the current user's role (xdXDocument:get-Role) is not supported by InfoPath Forms Services. ...
  49. The XPath functions xdEnvironment:IsMobile and xdEnvironment:IsBrowser are not supported in InfoPath 2003. The XPath expression ...
  50. The XPath must point to a field or group in the data source, or more than one field or group separated by the 'or' operator ...
  51. The xsf:hwsWorkflow element in the form definition (.xsf) file contains invalid syntax. Action Type ID duplicate was found: ...
  52. The xsf:script element in the form definition (.xsf) file is missing the following src attribute, or the attribute is not ...
  53. The xsl:stylesheet element had multiple xsl:template elements with no mode attribute. This is not supported. Using only the ...
  54. The _Startup or _Shutdown method in this form's code contains one or more calls to members of the Microsoft.Office.Interop.InfoPath.SemiTrust ...
  55. There are no digital signatures associated with this form. Before you submit the form, it is recommended that you sign it. ...
  56. There has been an error while loading the form. A required resource could not be downloaded. To try to resume the download, ...
  57. There is a control bound to a descendant ({0}) of this control's binding ({1}). But that control is not within this control ...
  58. There is a control within this control that is bound to a field or group ({0}) that is not a descendant of this control's ...
  59. There is a problem with the Web server. Make sure the Web server exists, try again later or contact the Web server administrator. ...
  60. There is a section or table bound to an ancestor ({0}) of this control's binding ({1}). But this control is not within that ...
  61. There is already a more recent version of this form template on the server. Either remove the existing form template from ...
  62. There was an error creating a document to print this form with Microsoft Office Word. To print the form in InfoPath instead, ...
  63. There was an unexpected error during field recognition. To fix this problem, import the document again with the "form layout ...
  64. These properties indicate the security settings for this form template. Trust level is either domain trust or full trust. ...
  65. This action can cause data loss in existing forms that are based on this form template. In particular, any forms that have ...
  66. This action requires a data connection. Click the Add button to add a data connection which you can use with this action. ...
  67. This change might invalidate some existing sessions. Sessions currently storing their state in the view will be terminated. ...
  68. This choice section is not inside a choice group or repeating choice group. It may have been dragged outside one of these ...
  69. This code was created with one of the InfoPath 2003 Toolkits for Microsoft Visual Studio. InfoPath needs to migrate the toolkit ...
  70. This control formats the data to show both date and time. Date and time cannot be displayed together in the same control ...
  71. This control formats the data to show both date and time. Date and time cannot be displayed together in the same control ...
  72. This control is not supported by InfoPath Forms Services. To publish this form template, the control must be removed or changed ...
  73. This control uses an XPath function that is not supported by InfoPath Forms Services. To publish this form template, the ...
  74. This copy of the form will not be signed because it is saved as source files. To sign the form permanently, select a certificate ...
  75. This data connection has been added to the form template, but InfoPath was unable to store a copy of the data for offline ...