Another Access 365 v2206 bug (from stackoverflow) (1 Viewer)

Mindflux

Member
Local time
Today, 01:52
Joined
Jun 25, 2022
Messages
42
Looks like rs.Fields defaults to a DAO.Field3 type (which seems new) instead of the prior default.

1656772286536.png



1656772269333.png



1656772302612.png


 
The Access team in aware of and investigating this one. Seems to be a bit of a black hole so far, though.
 
Why do you think "it is a bit of a black hole" ?
 
For info, MS has rolled back (withdrawn) the 2206 version.
Users will be prompted to 'update'. When they do so, 365 will in fact roll back to v2205 build 16.0.15225,20288 and 365 will report ii is up to date.
 
For info, MS has rolled back (withdrawn) the 2206 version.
Users will be prompted to 'update'. When they do so, 365 will in fact roll back to v2205 build 16.0.15225,20288 and 365 will report ii is up to date.
Mine didn't even ask, it just rolled itself back over the long weekend.
 
I have what I think is a new bug. After the recent update/rollback, my mouse has begun to behave erratically. Sometimes, it responds as it had in the past, but more often it appears to hang up briefly before responding. Sometimes it takes three or four attempts to place it in precisely the right location to hit a clickable spot.

Whereas I used to be able to click anywhere on a command button in a form, now I have to find some small spot on it that will respond.

The same is true for both single and double-clicks.

I have changed batteries, tried other mice (three altogether) and on different computers. All are the same. I have modified mouse settings to no avail.

Has anyone else noticed similar mouse behavior in the last couple of days?
 
I have what I think is a new bug. After the recent update/rollback, my mouse has begun to behave erratically. Sometimes, it responds as it had in the past, but more often it appears to hang up briefly before responding. Sometimes it takes three or four attempts to place it in precisely the right location to hit a clickable spot.

Whereas I used to be able to click anywhere on a command button in a form, now I have to find some small spot on it that will respond.

The same is true for both single and double-clicks.

I have changed batteries, tried other mice (three altogether) and on different computers. All are the same. I have modified mouse settings to no avail.

Has anyone else noticed similar mouse behavior in the last couple of days?

Can't say I've seen this one.
 

Users who are viewing this thread

Back
Top Bottom