Table view problem

[John Sh]

From time to time, in table view. I get this strange behaviour.
I am running Access 2019 and still on W10.

First image, Open table view. The first field is already highlighted.
Second image, select "Main_Family". All fields to the left are highlighted.
Third image, select record 107. All records above are highlighted.
It's as if I were holding down the "Shift" key.
If I try to sort a field, it is always the left most highlighted field that controls the sort.
If I restart Access this behaviour disappears for a while but will eventually return.

Why is it so and how do I stop it?

 

[June7]

I think I have experienced this sometime in the distant past.

Possible corruption of database or Access?

 

[BlueSpruce]

From time to time, in table view. I get this strange behaviour.
I am running Access 2019 and still on W10.

First image, Open table view. The first field is already highlighted.
Second image, select "Main_Family". All fields to the left are highlighted.
Third image, select record 107. All records above are highlighted.
It's as if I were holding down the "Shift" key.
If I try to sort a field, it is always the left most highlighted field that controls the sort.
If I restart Access this behaviour disappears for a while but will eventually return.

Why is it so and how do I stop it?
View attachment 121971View attachment 121972View attachment 121973

Did you by any chance ever exit or save the table, and then exit the accdb while those fields and records were highlighted?.. This reminds me of not removing code breaks in the VBE editor and exiting the accdb. Then itza real PITA to remove those sticky Gremlins

The easiest solution I suggest is to open the affected table, highlight and unhighlight the same field/records, save the table and exit the accdb. If that doesn't work, try importing the accdb into a new blank accdb.

 

[John Sh]

I think I have experienced this sometime in the distant past.

Possible corruption of database or Access?

I do a compact and repair on close so corruption is unlikely.
Also everything else is working as expected.
It just starts for no apparent reason and sometimes just stops doing it.
Usually restarting Access fixes it for a while.
Just a nuisance really, especially when trying to sort a field.

 

[John Sh]

Did you by any chance ever exit or save the table, and then exit the accdb while those fields and records were highlighted?.. This reminds me of not removing code breaks in the VBE editor and exiting the accdb. Then itza real PITA to remove those sticky Gremlins

The easiest solution I suggest is to open the affected table, highlight and unhighlight the same field/records, save the table and exit the accdb. If that doesn't work, try importing the accdb into a new blank accdb.

1} No.
2) The test accdb is regularly replaced with the active file, although I don't delete one and paste in the other.
The behaviour has persisted over multiple copies of the accdb.

I have to replace my very old cpu with one compatible with W11.
I'll see if that makes a difference when the new cpu arrives.
Thank you both.
John

 

[BlueSpruce]

I do a compact and repair on close so corruption is unlikely.

I hope you're not setting Compact/Repair on close in Access Options to automatically do it every time. That is known to cause corruption problems. I only CR after making frontend modifications and after first making a backup of backend tables if there's a data corruption problem.

 

[DHookom]

I would try a different mouse.

 

[BlueSpruce]

I would try a different mouse.

The OP said he's using an old PC and thinks a new one running Win11 is the solution. I think Win11 hurts more than helps. Anything new that Microsoft puts out has bugs. They have no QA, we the users are the alpha testers.