Text Boxes FLICKER - next record only.

[ThomasAJ]

I am aware of the 'unattached label on page of tab control pre Access 2003
SP3 etc.' issue as worked around by Allen Brown in
http://allenbrowne.com/ser-46.html.

This may be similar but different. The contents of text boxes do not flicker
when the mouse cursor is passed over.

System is Access 2003 SP3 over Terminal Services on Server 2008 running
Vista Themes.

The text boxes on pages of tab controls display their contents 3 times when
showing the next record. I know it's 3 times as on a slow remote computer
using Terminal Services I see the data 3 times. This causes problems for a
few users as you can imagine.

The above workaround might solve the problem but I thought I'd ask anyway.

 

[Jeanette Cunningham]

Hi Thomas,
I have seen a similar problem using A2007 on Vista with themed controls
turned on. I haven't tried it with themed controls turned off.
I had a form with an unbound text box in the form's header.
That text box had a control source like = =IIf(FormHasData([Form]),
([MainName]), "")

When the form opened, the text box flashed 3 times.
The reason seems to be that the form's current event runs 3 times instead of
just the one time (that it is easy to assume would be the case).
I used code that turned Echo off at the start of the event and turned echo
back on in the exit event of the procedure.
I suspect that you could use the Repaint instead of Echo, but haven't tried
this.
For me the issue happened when I used a requery to synchronize the form's
move to the next record in the recordset clone with another open form.

Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

 

[ThomasAJ]

Sorry should have mentioned this - but my Current Event runs ONCE only.

Just tested this now (again).

--
Regards
Tom

Hi Thomas,
I have seen a similar problem using A2007 on Vista with themed controls
turned on. I haven't tried it with themed controls turned off.
I had a form with an unbound text box in the form's header.
That text box had a control source like = =IIf(FormHasData([Form]),
([MainName]), "")

When the form opened, the text box flashed 3 times.
The reason seems to be that the form's current event runs 3 times instead of
just the one time (that it is easy to assume would be the case).
I used code that turned Echo off at the start of the event and turned echo
back on in the exit event of the procedure.
I suspect that you could use the Repaint instead of Echo, but haven't tried
this.
For me the issue happened when I used a requery to synchronize the form's
move to the next record in the recordset clone with another open form.

Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

 

[Jeanette Cunningham]

Are you sure? In A2003, my Current event runs twice on all forms.

Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

Sorry should have mentioned this - but my Current Event runs ONCE only.

Just tested this now (again).

--
Regards
Tom

Hi Thomas,
I have seen a similar problem using A2007 on Vista with themed controls
turned on. I haven't tried it with themed controls turned off.
I had a form with an unbound text box in the form's header.
That text box had a control source like = =IIf(FormHasData([Form]),
([MainName]), "")

When the form opened, the text box flashed 3 times.
The reason seems to be that the form's current event runs 3 times instead
of
just the one time (that it is easy to assume would be the case).
I used code that turned Echo off at the start of the event and turned
echo
back on in the exit event of the procedure.
I suspect that you could use the Repaint instead of Echo, but haven't
tried
this.
For me the issue happened when I used a requery to synchronize the form's
move to the next record in the recordset clone with another open form.

Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

I am aware of the 'unattached label on page of tab control pre Access
2003
SP3 etc.' issue as worked around by Allen Brown in
http://allenbrowne.com/ser-46.html.

This may be similar but different. The contents of text boxes do not
flicker
when the mouse cursor is passed over.

System is Access 2003 SP3 over Terminal Services on Server 2008 running
Vista Themes.

The text boxes on pages of tab controls display their contents 3 times
when
showing the next record. I know it's 3 times as on a slow remote
computer
using Terminal Services I see the data 3 times. This causes problems
for a
few users as you can imagine.

The above workaround might solve the problem but I thought I'd ask
anyway.

 

[ThomasAJ]

Well I put a break on the END SUB statement and it broke only once per record
though I did notice a calculated text box or 2 did have ERROR in it. Hmm...

I could add a count text box in the header area and increment it in the
current event and see what numbers pop up.

Anyway I must go out now so I'll try the 'count' later - thanks for your
help so far.
--
Regards
Tom

Are you sure? In A2003, my Current event runs twice on all forms.

Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

Sorry should have mentioned this - but my Current Event runs ONCE only.

Just tested this now (again).

--
Regards
Tom

Hi Thomas,
I have seen a similar problem using A2007 on Vista with themed controls
turned on. I haven't tried it with themed controls turned off.
I had a form with an unbound text box in the form's header.
That text box had a control source like = =IIf(FormHasData([Form]),
([MainName]), "")

When the form opened, the text box flashed 3 times.
The reason seems to be that the form's current event runs 3 times instead
of
just the one time (that it is easy to assume would be the case).
I used code that turned Echo off at the start of the event and turned
echo
back on in the exit event of the procedure.
I suspect that you could use the Repaint instead of Echo, but haven't
tried
this.
For me the issue happened when I used a requery to synchronize the form's
move to the next record in the recordset clone with another open form.

Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia


I am aware of the 'unattached label on page of tab control pre Access
2003
SP3 etc.' issue as worked around by Allen Brown in
http://allenbrowne.com/ser-46.html.

This may be similar but different. The contents of text boxes do not
flicker
when the mouse cursor is passed over.

System is Access 2003 SP3 over Terminal Services on Server 2008 running
Vista Themes.

The text boxes on pages of tab controls display their contents 3 times
when
showing the next record. I know it's 3 times as on a slow remote
computer
using Terminal Services I see the data 3 times. This causes problems
for a
few users as you can imagine.

The above workaround might solve the problem but I thought I'd ask
anyway.

 

[Jeanette Cunningham]

I put a break on the start of the current event and watch how many times it
is called.
The other thing you could try instead of using echo, is to turn screen
updating on and off.


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

Well I put a break on the END SUB statement and it broke only once per
record
though I did notice a calculated text box or 2 did have ERROR in it.
Hmm...

I could add a count text box in the header area and increment it in the
current event and see what numbers pop up.

Anyway I must go out now so I'll try the 'count' later - thanks for your
help so far.
--
Regards
Tom

Are you sure? In A2003, my Current event runs twice on all forms.

Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

Sorry should have mentioned this - but my Current Event runs ONCE only.

Just tested this now (again).

--
Regards
Tom


:

Hi Thomas,
I have seen a similar problem using A2007 on Vista with themed
controls
turned on. I haven't tried it with themed controls turned off.
I had a form with an unbound text box in the form's header.
That text box had a control source like = =IIf(FormHasData([Form]),
([MainName]), "")

When the form opened, the text box flashed 3 times.
The reason seems to be that the form's current event runs 3 times
instead
of
just the one time (that it is easy to assume would be the case).
I used code that turned Echo off at the start of the event and turned
echo
back on in the exit event of the procedure.
I suspect that you could use the Repaint instead of Echo, but haven't
tried
this.
For me the issue happened when I used a requery to synchronize the
form's
move to the next record in the recordset clone with another open form.

Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia


I am aware of the 'unattached label on page of tab control pre Access
2003
SP3 etc.' issue as worked around by Allen Brown in
http://allenbrowne.com/ser-46.html.

This may be similar but different. The contents of text boxes do not
flicker
when the mouse cursor is passed over.

System is Access 2003 SP3 over Terminal Services on Server 2008
running
Vista Themes.

The text boxes on pages of tab controls display their contents 3
times
when
showing the next record. I know it's 3 times as on a slow remote
computer
using Terminal Services I see the data 3 times. This causes problems
for a
few users as you can imagine.

The above workaround might solve the problem but I thought I'd ask
anyway.

 

[Jeanette Cunningham]

Oops . . .
to turn screen updating on and off, you use DoCmd.Echo True, DoCmd.Echo
False.
It is Excel that has a method called Application.ScreenUpdating.
If that doesn't help, there is an api to try.


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

I put a break on the start of the current event and watch how many times it
is called.
The other thing you could try instead of using echo, is to turn screen
updating on and off.


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

Well I put a break on the END SUB statement and it broke only once per
record
though I did notice a calculated text box or 2 did have ERROR in it.
Hmm...

I could add a count text box in the header area and increment it in the
current event and see what numbers pop up.

Anyway I must go out now so I'll try the 'count' later - thanks for your
help so far.
--
Regards
Tom

Are you sure? In A2003, my Current event runs twice on all forms.

Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia


Sorry should have mentioned this - but my Current Event runs ONCE
only.

Just tested this now (again).

--
Regards
Tom


:

Hi Thomas,
I have seen a similar problem using A2007 on Vista with themed
controls
turned on. I haven't tried it with themed controls turned off.
I had a form with an unbound text box in the form's header.
That text box had a control source like = =IIf(FormHasData([Form]),
([MainName]), "")

When the form opened, the text box flashed 3 times.
The reason seems to be that the form's current event runs 3 times
instead
of
just the one time (that it is easy to assume would be the case).
I used code that turned Echo off at the start of the event and turned
echo
back on in the exit event of the procedure.
I suspect that you could use the Repaint instead of Echo, but haven't
tried
this.
For me the issue happened when I used a requery to synchronize the
form's
move to the next record in the recordset clone with another open
form.

Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia


I am aware of the 'unattached label on page of tab control pre
Access
2003
SP3 etc.' issue as worked around by Allen Brown in
http://allenbrowne.com/ser-46.html.

This may be similar but different. The contents of text boxes do
not
flicker
when the mouse cursor is passed over.

System is Access 2003 SP3 over Terminal Services on Server 2008
running
Vista Themes.

The text boxes on pages of tab controls display their contents 3
times
when
showing the next record. I know it's 3 times as on a slow remote
computer
using Terminal Services I see the data 3 times. This causes
problems
for a
few users as you can imagine.

The above workaround might solve the problem but I thought I'd ask
anyway.

 

[ThomasAJ]

The Current Event runs ONCE ONLY per record 100% (a count stored in the
header).

ECHO makes no difference.
--
Regards
Tom

I put a break on the start of the current event and watch how many times it
is called.
The other thing you could try instead of using echo, is to turn screen
updating on and off.


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

Well I put a break on the END SUB statement and it broke only once per
record
though I did notice a calculated text box or 2 did have ERROR in it.
Hmm...

I could add a count text box in the header area and increment it in the
current event and see what numbers pop up.

Anyway I must go out now so I'll try the 'count' later - thanks for your
help so far.
--
Regards
Tom

Are you sure? In A2003, my Current event runs twice on all forms.

Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia


Sorry should have mentioned this - but my Current Event runs ONCE only.

Just tested this now (again).

--
Regards
Tom


:

Hi Thomas,
I have seen a similar problem using A2007 on Vista with themed
controls
turned on. I haven't tried it with themed controls turned off.
I had a form with an unbound text box in the form's header.
That text box had a control source like = =IIf(FormHasData([Form]),
([MainName]), "")

When the form opened, the text box flashed 3 times.
The reason seems to be that the form's current event runs 3 times
instead
of
just the one time (that it is easy to assume would be the case).
I used code that turned Echo off at the start of the event and turned
echo
back on in the exit event of the procedure.
I suspect that you could use the Repaint instead of Echo, but haven't
tried
this.
For me the issue happened when I used a requery to synchronize the
form's
move to the next record in the recordset clone with another open form.

Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia


I am aware of the 'unattached label on page of tab control pre Access
2003
SP3 etc.' issue as worked around by Allen Brown in
http://allenbrowne.com/ser-46.html.

This may be similar but different. The contents of text boxes do not
flicker
when the mouse cursor is passed over.

System is Access 2003 SP3 over Terminal Services on Server 2008
running
Vista Themes.

The text boxes on pages of tab controls display their contents 3
times
when
showing the next record. I know it's 3 times as on a slow remote
computer
using Terminal Services I see the data 3 times. This causes problems
for a
few users as you can imagine.

The above workaround might solve the problem but I thought I'd ask
anyway.

 

[Jeanette Cunningham]

Well, I am stumped - the description sounds exactly like the thing that
happens with my unbound text box with a control source using = a field in
the form's recordsource.
Good luck with finding a work around for this. I know how unprofessional it
looks from what I saw in my app.


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

The Current Event runs ONCE ONLY per record 100% (a count stored in the
header).

ECHO makes no difference.
--
Regards
Tom

I put a break on the start of the current event and watch how many times
it
is called.
The other thing you could try instead of using echo, is to turn screen
updating on and off.


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

Well I put a break on the END SUB statement and it broke only once per
record
though I did notice a calculated text box or 2 did have ERROR in it.
Hmm...

I could add a count text box in the header area and increment it in the
current event and see what numbers pop up.

Anyway I must go out now so I'll try the 'count' later - thanks for
your
help so far.
--
Regards
Tom


:

Are you sure? In A2003, my Current event runs twice on all forms.

Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia


Sorry should have mentioned this - but my Current Event runs ONCE
only.

Just tested this now (again).

--
Regards
Tom


:

Hi Thomas,
I have seen a similar problem using A2007 on Vista with themed
controls
turned on. I haven't tried it with themed controls turned off.
I had a form with an unbound text box in the form's header.
That text box had a control source like =
=IIf(FormHasData([Form]),
([MainName]), "")

When the form opened, the text box flashed 3 times.
The reason seems to be that the form's current event runs 3 times
instead
of
just the one time (that it is easy to assume would be the case).
I used code that turned Echo off at the start of the event and
turned
echo
back on in the exit event of the procedure.
I suspect that you could use the Repaint instead of Echo, but
haven't
tried
this.
For me the issue happened when I used a requery to synchronize the
form's
move to the next record in the recordset clone with another open
form.

Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia


I am aware of the 'unattached label on page of tab control pre
Access
2003
SP3 etc.' issue as worked around by Allen Brown in
http://allenbrowne.com/ser-46.html.

This may be similar but different. The contents of text boxes do
not
flicker
when the mouse cursor is passed over.

System is Access 2003 SP3 over Terminal Services on Server 2008
running
Vista Themes.

The text boxes on pages of tab controls display their contents 3
times
when
showing the next record. I know it's 3 times as on a slow remote
computer
using Terminal Services I see the data 3 times. This causes
problems
for a
few users as you can imagine.

The above workaround might solve the problem but I thought I'd
ask
anyway.