May 29 2022 07:38 PM
May 29 2022 07:38 PM
There has been an issue regarding Access 2019 displaying #Deleted status on certain table, for only certain windows user profile.
Based on my analysis:
1. This happen to only certain user profile. If I login into the windows using another profile and open the table, the data will be normally displayed.
2. This table are linked table with SQL server 2016, so I have check and find that the table have NVARCHAR field. I try to change the field type to VARCHAR, refresh the table link, then the data can be viewed again.
1. Delete the user profile and login again. Solve the problems but not sure if it will happen again in the future.
2. Installing Access Runtime. Solve the problems but at the same time i can't debug the program if there something wrong with it.
Does anyone have any idea what happen because i am really lost right now.
May 30 2022 07:25 AM
I'm having a similar issues I found this... I can't use the work arrounds he proposed but maybe your can
May 30 2022 08:09 AM
May 31 2022 12:20 AM
May 31 2022 09:31 AM - edited May 31 2022 09:33 AM
So to be clear.
If so, we need to know more about YOUR specific situation please.
May 31 2022 12:19 PM - edited May 31 2022 12:24 PM
I can confirm that we are having a very similar issue on some machines. Afflicted machines have MS 365 Office Version 2205 Build 15225.20204 CTR and our single machine which is working normally is on 2204 (Build 15128.20248). Reviewing version notes there doesn't seem to be changes that would cause this but still it has. I changed the data format to VarChar and can view the data normally. Going to stick to that for now.
May 31 2022 07:51 PM
HQ already request us to downgrade the Access to 2016 version. So that is our solution for now.
Jun 01 2022 05:18 AM
Jun 01 2022 04:11 PM
Jun 01 2022 04:47 PM
Jun 01 2022 05:25 PM
@Jlorbz The fact that MS has released, or will release, a specific fix confirms it is a bug that needed to be fixed.
Others are less formal in documenting the on-going problems.
Jun 02 2022 05:50 AM
Jun 02 2022 05:54 AM
Jun 02 2022 06:01 AM - edited Jun 02 2022 06:01 AM
Jun 02 2022 06:09 AM - edited Jun 02 2022 06:13 AM
Many, perhaps most, of the MS Access MVPs I know already have stopped
accepted accepting auto-updates, or gone to a semi-annual channel so that they stand a chance of such bugs being fixed before they get to them. It's a trade-off between being on the "cutting edge" or the "bleeding edge", you might say. And that's a very fine line, indeed :)
Jun 02 2022 06:26 AM