Office System 2010

  1. The expression you entered has invalid parentheses.@You may have used the parenthesis syntax for an identifier in a query. ...
  2. The expression you entered in the Specification Name argument exceeds the 64-character limit.@Select one of the existing ...
  3. The expression you entered refers to an object that is closed or doesn't exist.@For example, you may have assigned a form ...
  4. The expression you entered requires the control to be in the active window.@Try one of the following: Open or select a form ...
  5. The expression |2 you entered as the event property setting produced the following error: |1.@* The expression may not result ...
  6. The expression |2 you entered in the form control's ValidationRule property contains the error |1.@|9 can't parse the ValidationRule ...
  7. The extension " " is not loaded. This version of Outlook only supports Microsoft Exchange 4.0 extensions. Change the version ...
  8. The extension string is not specified or is invalid. Specify an extension string that does not contain the following characters: ...
  9. The extension string is not specified or is invalid. Specify an extension string that does not contain the following characters: ...
  10. The extension you have entered is invalid. Please enter the extension(s) with " " (space), "," (comma), or ";" (semi-colon) ...
  11. The external content type cannot be saved, because its version in the Business Data Connectivity Metadata Store has reached ...
  12. The external content type definition includes properties on elements that no longer exist on the data source: {0}. Do you ...
  13. The External Content Type Layout at {0} is invalid. The top level element must derive from Microsoft.Office.BusinessAppl ...
  14. The external content type minor version cannot be incremented anymore. Manually increment the version number and try save ...
  15. The External Content Type requires a Filter definition in order to narrow your search. Contact your system administrator. ...
  16. The external content type version number is invalid. Please make sure it complies with the following format: N.N.N.N where ...
  17. The External Content Type view context could not be found for these parameters: ExternalContentTypeNamespace='{0}', ExternalContentType ...
  18. The external data range contains one or more columns that were added in Excel. When you publish this data to the Web with ...
  19. The External Item Picker is not supported in user code solutions. To publish this form to SharePoint, use the administrator-approved ...
  20. The external query '%1' from the workbook '%2' was stopped because it did not complete in %3 seconds. Please update the Maximum ...
  21. The external query '%1' in %2 did not run due to the AllowExternalData setting of %3. To allow external data connections, ...
  22. The external stylesheet dependencies for this document have changed. In order to see these changes, you must save and reload ...
  23. The external system {0} contains existing external content types. These must be deleted before the external system can be ...
  24. The external task ID number is not valid.}The ID number entered for the task in the external project either does not exist ...
  25. The Extra Content task pane still contains items that did not fit into your changed publication. To delete these items and ...
  26. The farm account username and password must be specified during upgrade. This account will be used as the process identity ...
  27. The farm account username and password must be specified if the SQL Server installation resides on any machine other than ...
  28. The farm search service account is a built-in account like Local Service or Network Service. This account is used to securely ...
  29. The feature '|2' (id: |3) is dependent on feature '|0' (id: |1), which is hidden and has activation dependencies. Hidden ...
  30. The feature '|2' (id: |3) is dependent on feature '|0' (id: |1, version: |5). Version |4 of feature '|0' is installed and ...
  31. The feature being activated is a |2 scoped feature which has a dependency on a |0 scoped feature which has not been activated. ...
  32. The feature failed to activate because a list at '{0}' already exists in this site. Delete or rename the list and try activating ...
  33. The feature with ID '|0' is still activated within this farm or stand alone installation. Deactivate this feature in the ...
  34. The feature with ID '|0' is still activated within this farm or stand alone installation. This feature is active at multiple ...
  35. The feature with Id |0 is referenced in the database |1], but is not installed on the current farm. The missing feature may ...
  36. The feature you are trying to activate is dependent on a hidden feature. The specified hidden feature has additional dependencies ...
  37. The feature you are trying to activate is dependent on another feature {0} contained in the solution titled {1} which is ...
  38. The feature you are trying to activate is dependent on another feature {0} contained in the solution {1} which is not installed. ...
  39. The feature you are trying to activate is dependent on another feature {0} contained in the solution {1} which is not installed. ...
  40. The feature you are trying to activate is dependent on another feature {0} contained in the solution {1} which is not installed. ...
  41. The feature you are trying to activate is dependent on another feature {0} in another solution name. This solution can be ...
  42. The feature you are trying to activate is dependent on another feature {0} in another solution {1}. this solution can be ...
  43. The feature you are trying to activate is dependent on another feature {0} in another solution {1}. This solution has been ...
  44. The feature you are trying to activate is dependent on another feature {0} in another solution {1}. This solution is already ...
  45. The feature you are trying to activate is from the scope {0}. It is dependent on another feature with lower scope {1} . It ...
  46. The feature you are trying to use is not supported in your Web browser. You must install Microsoft Internet Explorer version ...
  47. The field " " will be removed from the list of available fields but will remain in all items in which it was used. Do you ...
  48. The field "%1" already exists in the design but has a different field type than the field being imported. Please fix the ...
  49. The field '{0}' could not be read because it is the primary key of the record being created. This field's value will be available ...
  50. The field '|' cannot be modified because it contains invalid characters, invalid punctuation, or an existing field name. ...
  51. The field '|0' cannot be updated. The field is in a field collection that cannot be updated, such as one returned as part ...
  52. The field '|1' could not be changed because the record is not currently updatable. Use EditRecord to make the record updatable. ...
  53. The field '|1' could not be read because it is the primary key of the record being created. This field's value will be available ...
  54. The field cannot be added to the enterprise because of one of the following reasons: \- The formula contains a syntax error. ...
  55. The field cannot be copied because the formula contains a syntax error or a reference to an unrecognized field or function ...
  56. The field could not be added on the server. Synchronize with the server and remove any references to hidden, lookup, AutoNumber, ...
  57. The field could not be deleted on the server. Synchronize with the server and verify that no other field references this ...
  58. The field description is optional. It helps you describe the field and is also displayed in the status bar when you select ...
  59. The field has been set to roll down from the ^1field. Change the option for the ^1field to None if you want this field to ...
  60. The field name " " is invalid because it conflicts with a built-in property name. To use a built in field, remove the definition ...
  61. The field name is missing in row |.@You haven't selected a matching field for this relationship in each row of the grid.@Select ...
  62. The field name that you defined for data source element {0} is already used for another data source element defined on this ...
  63. The field name you entered does not follow |9 object-naming rules. If you pasted the name from another application, try pressing ...
  64. The field name you entered exceeds the 64-character limit of the LinkMasterFields property.@When you use the Relationships ...
  65. The field name \"^1\" cannot be copied because \"^2\" already contains a field with that name.}Do you want to copy all other ...
  66. The field named '{0}' and described in the TypeDescriptor for the Return parameter was not returned by the backend system". ...
  67. The field named '{0}' and described in the TypeDescriptor for the Return parameter was not returned by the backend system". ...
  68. The field named '{0}' and described in the TypeDescriptor for the Return parameter was not returned by the External System. ...
  69. The Field named '{0}' contains an Identifier which is not read only. The Update operation requires a corresponding PreUpdaterField ...
  70. The field named '{0}' is defined by the Entity (External Content Type) as being of Type '{1}', but the External System returned ...
  71. The field named '{0}' is defined by the Entity as being of Type '{1}', but the back end system returned a value of Type '{2}'". ...
  72. The field named '{0}' is defined by the Entity as being of Type '{1}', but the back end system returned a value of Type '{2}'". ...
  73. The Field named '{0}' is provided as input but cannot be found on the '{4}' method signature for Method with Name '{1}' on ...
  74. The field was successfully added to Project Server.}In order to view and use the enterprise field in the project, you will ...
  75. The field you are deleting will be removed from the list of available fields, but will remain in all items in which it was ...