Subform Flickers w/ Calculated Control

  • Thread starter Thread starter JP
  • Start date Start date
J

JP

I have a subform in continuous mode. In Access 2003 (Win XP), I have found
that if the first control in the subform is a textbox with a calculated
value, then the subform will flicker. That is:

The controlsource for the first control in the detail section of the subform
(in this case a textbox) is a calculation, for example:

=iif([Exclusive_Group] and [First_Record], "#", "")

When opened, the subform keeps recycling (each entire row rapidly and in
succession blinks). While this is happening, CPU utilization is at 100%,
the form footer (a sum of one of the form fields) never displays, and it's
impossible to actually enter any data. In fact, it usually won't respond to
a form close command and I usually have to CTRL-ALT-DEL to terminate the
form (and, of course, Access itself).

This only happens under Access 2003. I have an Access 2000 machine and have
not had this problem.

Is this a known behavior and if so, is there a correction? I've been able
to program around it in this case, but would prefer to know that there is a
solution to the problem.
 
I don't believe that a simple calculation in a control in the subform would
cause a flicking problem. Perhaps the complexity or accessibily of your data
source is causing the problem - I have seen a similar effect for
multi-layered subqueries in databases working on a slow network.

If this is the same form as listed in
http://msdn.microsoft.com/newsgroup...orms&mid=8483ab53-d759-4551-b04c-1d71b1f2a42e,
there may be a common source for your problems.

Have you tried testing this database on a different PC? Looking at your
other postings, you might want to try testing for these probelms on another
PC.

Marvin
 
Thanks for your reply.

It is not the same form as the other post I had this morning.

This problem (the flickering) only happens in Access 2003 (I have tested it
on other machines with both A2003 and A2000). The other problem (the After
Update not firing) happens under both A2003 and A2000 on every machine I've
tried it on.

I have determined that by moving the calculated control to be AFTER the
first real input field (i.e., further down in the tab sequence than a bound
textbox), the flickering does NOT occur.

Weird.


Marvin said:
I don't believe that a simple calculation in a control in the subform would
cause a flicking problem. Perhaps the complexity or accessibily of your data
source is causing the problem - I have seen a similar effect for
multi-layered subqueries in databases working on a slow network.

If this is the same form as listed in
http://msdn.microsoft.com/newsgroup...orms&mid=8483ab53-d759-4551-b04c-1d71b1f2a42e,
there may be a common source for your problems.

Have you tried testing this database on a different PC? Looking at your
other postings, you might want to try testing for these probelms on another
PC.

Marvin

JP said:
I have a subform in continuous mode. In Access 2003 (Win XP), I have found
that if the first control in the subform is a textbox with a calculated
value, then the subform will flicker. That is:

The controlsource for the first control in the detail section of the subform
(in this case a textbox) is a calculation, for example:

=iif([Exclusive_Group] and [First_Record], "#", "")

When opened, the subform keeps recycling (each entire row rapidly and in
succession blinks). While this is happening, CPU utilization is at 100%,
the form footer (a sum of one of the form fields) never displays, and it's
impossible to actually enter any data. In fact, it usually won't respond to
a form close command and I usually have to CTRL-ALT-DEL to terminate the
form (and, of course, Access itself).

This only happens under Access 2003. I have an Access 2000 machine and have
not had this problem.

Is this a known behavior and if so, is there a correction? I've been able
to program around it in this case, but would prefer to know that there is a
solution to the problem.
Click to expand...
Click to expand...
 
That does sound strange. I guess it's a bug. If you need to keep the
apparent order of the controls, maybe you cold place in a dummy control and
set its visible property to false.

Hope you find a resolution.

JP said:
Thanks for your reply.

It is not the same form as the other post I had this morning.

This problem (the flickering) only happens in Access 2003 (I have tested it
on other machines with both A2003 and A2000). The other problem (the After
Update not firing) happens under both A2003 and A2000 on every machine I've
tried it on.

I have determined that by moving the calculated control to be AFTER the
first real input field (i.e., further down in the tab sequence than a bound
textbox), the flickering does NOT occur.

Weird.


Marvin said:
I don't believe that a simple calculation in a control in the subform would
cause a flicking problem. Perhaps the complexity or accessibily of your data
source is causing the problem - I have seen a similar effect for
multi-layered subqueries in databases working on a slow network.

If this is the same form as listed in
http://msdn.microsoft.com/newsgroup...orms&mid=8483ab53-d759-4551-b04c-1d71b1f2a42e,
there may be a common source for your problems.

Have you tried testing this database on a different PC? Looking at your
other postings, you might want to try testing for these probelms on another
PC.

Marvin

JP said:
I have a subform in continuous mode. In Access 2003 (Win XP), I have found
that if the first control in the subform is a textbox with a calculated
value, then the subform will flicker. That is:

The controlsource for the first control in the detail section of the subform
(in this case a textbox) is a calculation, for example:

=iif([Exclusive_Group] and [First_Record], "#", "")

When opened, the subform keeps recycling (each entire row rapidly and in
succession blinks). While this is happening, CPU utilization is at 100%,
the form footer (a sum of one of the form fields) never displays, and it's
impossible to actually enter any data. In fact, it usually won't respond to
a form close command and I usually have to CTRL-ALT-DEL to terminate the
form (and, of course, Access itself).

This only happens under Access 2003. I have an Access 2000 machine and have
not had this problem.

Is this a known behavior and if so, is there a correction? I've been able
to program around it in this case, but would prefer to know that there is a
solution to the problem.
Click to expand...
Click to expand...
Click to expand...
 
Back
Top