Strange VBA editor typing behaviour

[stevekos07]

I don't know if there is already a solution posted for this one. I have upgraded to Access 2016, and for some reason now when trying to edit code in the VBA editor I have to fight some strange behaviour as I type. Often the options such as the ac... options just flash up and then disappear, and sometimes the cursor just changes position as I type. Because I touch type, I sometimes don't notice the random changes until several characters on and I have to go back and fight the editor to correct the syntax.

This is VERY frustrating! Can anyone help with advice on this?

 

[stevekos07]

I found a solution, thanks! It is to do with a timer running on open sheets in the background. I find the behaviour stops when I close the affected sheets. Cheers!

 

[pbaldy]

Thanks for the update. That is the usual suspect and the normal solution.

 

[isladogs]

Well done for finding the solution so quickly.
It took me months to work it out on my own applications ....

 

[Pat Hartman]

I accept that there are some valid reasons for using a Timer but I've only actually created one app that used them. Luckily I discovered early on the problem they cause for development. I implemented code in the login form such that if it was me logged in, the timers were shut down. That way they didn't interfere with any of my design changes. If I wanted to actually test with the timers on, I logged in as a different user.

 

[isladogs]

I accept that there are some valid reasons for using a Timer but I've only actually created one app that used them. Luckily I discovered early on the problem they cause for development. I implemented code in the login form such that if it was me logged in, the timers were shut down. That way they didn't interfere with any of my design changes. If I wanted to actually test with the timers on, I logged in as a different user.

That's exactly the solution I used as well .... it just took me longer than it should to link the dots!

In my case the timer is used in the persistent connection hidden form.
Its purpose is to check for user activity every 30 seconds.
If there is no activity detected within a specified period e.g. 20 mins, the database is closed after a user warning.
This ensures all FE databases are closed to allow overnight admin tasks but also allows the sysadmin to close the database for essential maintenance.

By definition, none of that is needed in development mode!

 

[nortonm]

I've had this problem too a few times, and it normally goes when I compile the database, which in my case at least usually finds code referring to now deleted controls for example. Delete the control reference from the code, and recompile until no more issues found.