Auto typing bug

[Freshman]

Hi all,

I'm not even sure what to call this bug but let me try explain.
Sometimes when opening Access and entering some code in the VBA screen the system starts messing with my typing in a bad way.

For example I would want to type the following: "me.mycombo.requery"
The normal state of affairs as you all know is that Access would assist by bringing up all fields starting with a "m" straight after you hit the "." after typing "me" but in this case after I then start typing the first bit of "mycombo" like I normally do, the letters would just disappear or my cursor would move to the end or to another place in the line. Even when I then get to the second "." and expecting the next keywords to appear, they would appear for a brief moment and then disappear forcing me to type in "requery" manually so to speak. And even while I'm busy typing in "requery" my cursor would jump around to cause me to make a spelling mistake.
It is SO irritating as you can imagine.
Although it does not happen in any other app I even changed my keyboard to try and resolve this.
Closing and re-opening Access sometimes helps but not all the time.
I sometimes need to do a "detect and repair" or even a reboot.

Has anyone ever experience this?
Having worked on Access 2003 for close to 15 years it only started happening in the last 6 months or so, so it might be a virus (I have done all scans).

Thanks
Pierre

 

[spikepl]

weird stuff can happen if you have a timer running

 

[JHB]

Have you tried to reinstall MS-Access?

 

[Freshman]

weird stuff can happen if you have a timer running

Nope - no event timers. It also happens on not just one of my databases. I had it happening on brand new projects I started from scratch.

 

[Freshman]

Have you tried to reinstall MS-Access?

It did it again this morning that is why I started this thread and I fixed it by doing a detect & repair. So in theory a total un-install and re-install might be the answer.
The only reason why I did not do it as yet is that I can't remember which service packs and hot fixes are the best to do and don't do.
I know there were some posts in the past regarding some hot fixes that must be skipped but can't remember which.
Maybe I must try find out exactly what to load to get back to where I'm now (without the bug ) and then do it.
Shout if you can shed some light

My About page shows this now:
Access 2003 (11.8321.8405) SP3

Access in the only Office Pro 2003 product loaded and then I also have the full Office Pro Plus 2010 loaded incl Access 2010 which I never use.

Thanks!

 

[Freshman]

Ok - I uninstalled and re-installed and then added SP3 and the following hotfix:
office2003-kb945674-glb.exe
This got me to 11.8204.8172
I read somewhere that 11.8321.8405 is the latest hotfix.
Anyone got a link to the hotfix?

Thanks again

 

[Freshman]

Don't worry I got it stored on my USB flash
I just hope this exercise solves my initial typing bug...

 

[JHB]

Why not use MS-Access 2010, instead of MS-Access 2003?
You could also use MS-Access 2010, to find out if the Auto typing work in that version.
When you write "detect & repair" do you mean "Compact & Repair"?

 

[Freshman]

I'm a die-hard 2003 user. I recon 2007 and upwards too much attention is paid to the User and the Developer is forgotten...just my feeling.
I charge more if I have to develop in 2007 or 2010

Nope - you'll find "Detect and repair" under the Help menu. It is almost like a re-install.
Even in Word and Excel 2003. It might be 2003-only - not sure

 

[JHB]

Hmm - I think it is more a matter of getting used to it than anything else!
I never get used to MS-Access 2003, (I better liked 2000 so I skipped 2003).
Afterwards I jumped directly from 2000 to 2010 and now I feel good with it!

 

[Galaxiom]

I'm a die-hard 2003 user.

Microsoft support for Office 2003 has ended.

I recon 2007 and upwards too much attention is paid to the User and the Developer is forgotten...just my feeling.

I don't see how you would come to that conclusion. I much prefer the design interface for the later versions of Access.

I continue to use mdb and mde files because I don't see any significant advantages in accdb and a big disadvantage that they don't support code signing. But I develop and run databses in Access 2010.