The following are known issues that you might encounter when using Microsoft Query or Microsoft Access to work with virtual tables.
In Microsoft Access, if a table contains cells that show #Deleted as the value instead of the expected data value, then the table might be using an invalid primary key. To diagnose this issue, check the primary key values in the table and the data type of the primary key column, and verify if either of the following situations apply:
To resolve this issue, make sure that the table does not contain any rows that share the same primary key value.
To resolve this issue, convert the column to another data type, such as SQL_INTEGER or SQL_CHAR.
In Microsoft Access, if you encounter an error message stating "[ColumnName] is not a valid name" (where [ColumnName] is the name of a column in your result set), then the column name contains special characters that are not supported by the application.
In Microsoft Query, this issue returns an error message stating "Qualified column could not be bound".
If you are working with a NoSQL database, then this issue might be caused by the separator characters that the driver uses when generating a schema definition. To resolve this issue, change the ODBC column name in the schema definition (the
SQL Name) to a valid name, based on the following guidelines:
Simba ODBC drivers that support NoSQL databases include the Schema Editor application, which you can use to change the column names in the schema definition. For information about using the Schema Editor to rename columns in the schema definition, see the Schema Editor User Guide.