I want to stop forms from flickering when it receives focus...

[lcon2 via AccessMonster.com]

I have a program where the focus moves from one form to another and then the
focus is returned to the original form. When this action takes place, the
form’s caption bar that receives the focus turns is highlighted or turns
bright blue. What I would like to do is either freeze the screen or disable
the function that causes the form that has the focus to turn bright, because
the user does not need to know that the focus is shifting between forms and
the flickering is disconcerting to the eye.

While searching, I did find a routine that turned off the caption bar all
together, and that did have the effect of disabling the form’s caption that
received the focus from being highlighted. The procedure dealt with API?!
Not really sure what that is all about… but it did work.

Does anyone out there know how to achieve this while leaving the caption bar
intact?

Thanks

 

[Marshall Barton]

I have a program where the focus moves from one form to another and then the
focus is returned to the original form. When this action takes place, the
form’s caption bar that receives the focus turns is highlighted or turns
bright blue. What I would like to do is either freeze the screen or disable
the function that causes the form that has the focus to turn bright, because
the user does not need to know that the focus is shifting between forms and
the flickering is disconcerting to the eye.

While searching, I did find a routine that turned off the caption bar all
together, and that did have the effect of disabling the form’s caption that
received the focus from being highlighted. The procedure dealt with API?!
Not really sure what that is all about… but it did work.

First, the question is why do you have to move the focus?
This is a rather unusual thing to do, unless you are leaving
the focus on the second form for user input (in which case
there is no prblem).

But to try to address your question, have you explored the
Echo method?

 

[lcon2 via AccessMonster.com]

First, the question is why do you have to move the focus?

This is a rather unusual thing to do, unless you are leaving
the focus on the second form for user input (in which case
there is no prblem).

I am trying to create a virtual keyboard so that my application can be run on
a tablet pc. I would provide the user with a keyboard than rely on
Microsoft’s keyboard. So the focus goes:
1. from my virtual keyboard
2. to my text box on the second form
3. back to my virtual keyboard.

Also, my keyboard allows the user to Tab from one control to another. In
order to accomplish this, my second form has to receive the focus.

The echo method does not work, the form receiving the focus still has its
caption bar highlighted.

 

[Marshall Barton]

I am trying to create a virtual keyboard so that my application can be run on
a tablet pc. I would provide the user with a keyboard than rely on
Microsoft’s keyboard. So the focus goes:
1. from my virtual keyboard
2. to my text box on the second form
3. back to my virtual keyboard.

Also, my keyboard allows the user to Tab from one control to another. In
order to accomplish this, my second form has to receive the focus.

The echo method does not work, the form receiving the focus still has its
caption bar highlighted.

Tough problem.

If Echo False sitll allows screen updates to be displayed, I
think you're out of luck here. Setting the focus to a
control on a form requires that the form be repainted. This
in turn brings the form to the front, etc. so I don't see
how you can avoid the flicker.

Maybe someone else has a better thought?

 

[Jesper Fjølner]

I am trying to create a virtual keyboard so that my application can be run
I seem to be able to move the focus from on text boxt to the next on another
form using
(with the forms keypreview set to true).

Forms!entryform!textbox.setfocus

Only the cursor is not showing on the in inactive form.
If I, with the mouse, activate the entry form the cursor is in the right
box.

When you say "Tab from one form to anther" I assume you mean pressing the
tab-button on your homemade keyboard?


Jesper

 

[Ken Snell [MVP]]

Sometimes DoCmd.Echo does not work well, but Application.Echo does work ok.

Which one was tried?

 

[lcon2 via AccessMonster.com]

Sometimes DoCmd.Echo does not work well, but Application.Echo does work ok.

Which one was tried?

Both of them.

 

[MacDermott]

How about implementing the virtual keyboard as a subform instead of a
separate form?

 

[lcon2 via AccessMonster.com]

How about implementing the virtual keyboard as a subform instead of a
separate form?

That would work, however I would have to go back and rework my entire
application, and I also don't think it looks as pretty.

 

[MacDermott]

When I developed a virtual keyboard for a VB6.0 application, I made it as a
separate ActiveX control - that worked pretty well.
ActiveX controls developed in VB6.0 can, with some limitations, be used on
Access forms. However, it rather sounds as if you have fixed on one idea
and aren't too interested in other approaches.

 

[lcon2 via AccessMonster.com]

However, it rather sounds as if you have fixed on one idea
and aren't too interested in other approaches.

I am interested in any approach that will fit my needs. The subform is a
good idea, except that quite a few of my forms are Continuous Forms.
Subforms do not work

 

[Guest]

Subforms can be placed in a header or footer of a continuous form just fine...

- Igor