Weird Form flashing when I enter new record.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a form that is continuous and has a Tab Control in the footer. The
Tab control has numberous fields on it. I've adjusted all field names so
that I don't get that damned "mouseover flicker" so that's not the problem.

Oh by the way, hey Microsoft, SINCE YOU KNOW THERE IS THIS MOUSEOVER FLICKER
PROBLEM WITH TAB CONTROLS, WHY THE HELL'O DON'T YOU PROVIDE A PATCH TO FIX
IT???!!! WHY AM I FORCED TO USE SOME BOGUS WORKAROUND WHERE I HAVE TO CHANGE
ALL MY LABELS TO FIELDS JUST TO MAKE IT NOT FLICKER? FER GOD'S SAKE MS, THIS
IS A TOTALLY BOGUS PROBLEM THAT YOU REFUSE TO FIX! FIX IT ALREADY! DIDN'T
THIS PROBLEM COME UP IN YOUR BETA TESTS?

Sorry, I just had to do that rant. I just get sick of crappy little things
like this in Access that MS is just too darn lazy to fix.

Meanwhile, back to the problem at hand. When I try to add a new record, the
whole form flickers like 15 times before it starts adding data.

Anyone know why this is and how it can be fixed?

Thanks!

Bill
 
Hi,


I doubt there is a Microsoft responsible person about planning and
internal resources allocation that hangs around this newsgroup, reading 99%
technically (rather than administratively) related post. You may be better
using their web site with regard to bugs, and may even ask to be in the next
public beta? At best, there is maybe a technical person from Microsoft that
would read your post, but do you think that developers decide by themselves
on what they have to work, and about what "bug" will be corrected next, or
not? You have to reach Microsoft administration, ... that is quite unlikely
to happen ... here.

In the meantime, form flickering is not necessary very reproducible (can
you illustrate the problem using a Northwind Form, as example?). Without any
further detail about YOUR design, it may be very hard to fix. There may be a
problem with the VBA code behind the form, there may be a problem with the
tab control itself too, but your description is just too generic to be
meaningful.



Vanderghast, Access MVP
 
Based upon my reading its yet another BUG in Access 2003. Hell, don't they
even test this software before they sell it to unsuspecting victims like me?

It seems to be a common problem.

Thanks anyway.

Bill
 
Back
Top