Minty
AWF VIP
- Local time
- Today, 15:09
- Joined
- Jul 26, 2013
- Messages
- 10,484
As per this thread here
Originally about Oracle, we have now seen this in two Azure BE client databases in the last 2 days, making me think another silent update has been applied.
It appears that some versions of Access can no longer see tables that have an nvarchar() primary key specified.
The fix appears to be to change the field to a varchar data type, or add a new primary key numeric ID, and set the original PK field to be unique and not allow nulls.
This should retain your functionality without a ton of reworking.
You have been warned.
My colleague can't see the same problem using 2204
I can using 2205 and I get the error
Originally about Oracle, we have now seen this in two Azure BE client databases in the last 2 days, making me think another silent update has been applied.
It appears that some versions of Access can no longer see tables that have an nvarchar() primary key specified.
The fix appears to be to change the field to a varchar data type, or add a new primary key numeric ID, and set the original PK field to be unique and not allow nulls.
This should retain your functionality without a ton of reworking.
You have been warned.
My colleague can't see the same problem using 2204
I can using 2205 and I get the error