Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Symptoms

Consider the following scenario:

  • You have a computer that is running Microsoft SharePoint Server 2010.

  • You have Access Services enabled in SharePoint Server 2010.

  • You publish a Microsoft Access 2010 database to Access Services.

  • You add a new record to a table in the database.

  • When you add the record, you receive a type mismatch error in the USysApplicationLog:

    Category: Execution
    Context: error_expression
    Description: Type mismatch
    ErrorNumber: -8084
    ObjectType: Macro
    SourceObject: Access_table.field

  • Then, you open the database by using Access 2010 and then add a new record to the same table

  • When you add the record, you receive the following error in USysApplicationLog: 

    Category: Execution
    Object Type: Macro
    SourceObject: [Access_table].[field]
    Description: Failed to evaluate expression 'error_expression': error value '#VALUE!'.
    Error Number: -8990
    Context: error_expression

In this scenario, you notice that Access Services and the Access 2010 client generate different error codes for the type mismatch error.

Cause

This issue occurs because of the way expressions are evaluated when you use Access Services in SharePoint Server 2010 and when you use Access 2010. The error codes represent the following errors:

  • Error code-8084 is an evaluation time error.

  • Error code -8990 is a parse time error.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×