Visual Basic editor misbehaves...

[Fred Boer]

Hello!

Running Windows XP Pro, Access XP ODE...

On two separate computers I continually have a problem with the editing code
in the Visual Basic Editor. It is as if the editor is out of sync with the
keyboard. For example:

I type "me.". The Editor shows the Intellisense list, but instead of waiting
for input from the keyboard, it immediately closes Intellisense, and then
highlights the code in red, as if I've hit Enter.

I type "me.controlname.visible=". I continue after the equals sign to try to
type "False". The Intellisense pops up, disappears, and suddenly the cursor
is placed to the left of the "F" I've already typed.

I simply type "If me.". It immediately turns red, even as I continue to
type...

Is anyone else having problems like this? It is *very* frustrating, since it
makes it impossible to use Intellisense, and almost impossible to type at
all...

Thanks!
Fred Boer

 

[Dirk Goldgar]

Hello!

Running Windows XP Pro, Access XP ODE...

On two separate computers I continually have a problem with the
editing code in the Visual Basic Editor. It is as if the editor is
out of sync with the keyboard. For example:

I type "me.". The Editor shows the Intellisense list, but instead of
waiting for input from the keyboard, it immediately closes
Intellisense, and then highlights the code in red, as if I've hit
Enter.

I type "me.controlname.visible=". I continue after the equals sign to
try to type "False". The Intellisense pops up, disappears, and
suddenly the cursor is placed to the left of the "F" I've already
typed.

I simply type "If me.". It immediately turns red, even as I continue
to type...

Is anyone else having problems like this? It is *very* frustrating,
since it makes it impossible to use Intellisense, and almost
impossible to type at all...

Thanks!
Fred Boer

It's a known problem, Fred -- you have a form open with an active Timer
event. Whenever the timer event fires, the VB Editor momentarily loses
focus, causing it to think you've finished typing. Close the form in
question, or disable its Timer event, while editing code.

 

[Fred Boer]

Dear Dirk:

Hallelujah! This has been such an annoyance for so long; thanks so much!

Fred

P.S. Kinda begs the question "Why did you put up with it so long before
posting the question?", doesn't it.... <g>

 

[Tony Toews]

P.S. Kinda begs the question "Why did you put up with it so long before
posting the question?", doesn't it.... <g>

BTDTGTTshirt. <smile>

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm