Screenjudder (Access 97 SR2)

Topic

New Reply

Strange one this – when clicking on certain controls the screen judders, rapidly switching between what looks like an interlaced, jagged image and the normal screen. The process is completely repeatable and only occurs on certain controls in the form.

My first suspicion was a graphic card but this is happening on a number of networked machines using the same copy of the database – don’t mention the advantages of a Front End – I know and I’d love to if only ‘they’ would let me

The problem happens when clicking in the same controls – this is what points me towards Access and not a graphic card problem.

Does anyone have any ideas?

Reply | Quote

Replies

When did this start happening?
I had a similar problem after I had Win95 reinstalled, it happended I needed the correct driver for my screen.
Pat

Reply | Quote

It may very well be Access in the sense that what you’ve told it to do is causing the screen to redraw itself. YOu need to take a look at what is going on behind the scenes when you click on those controls. Step through the code and see what’s going on. The cure may be as simple as turning Painting off temporarily while some code is completed and then setting Me.Painting = True after it’s finished.

Reply | Quote

Do these buttons modify any settings? Such as enable/disable, show/hide … If they do then try turning off screen repainting until the procedure is completed.

Reply | Quote

Thanks for those suggestions – unfortunately I haven’t got direct access to the database at the moment but I’ll see if any of those options help. As far as I remember there is no code attached to the controls and, in any case, it would have to be attached to the OnClick event as tabbing into the control does not cause the problem and the problem occurs before any changes are made.

I didn’t create the database so I’m not sure that there isn’t something attached to the OnClick property. This problems happens on text boxes so I would be suprised if there was (but, hey, you never know!)

I think that maybe the graphics card drivers would be a good place to start – at least that eliminates any strange ‘incompatability features’ that may be going on.

Thanks again.

Reply | Quote

I’ve seen an effect like what you are describing, and it was completely caused by Access. What caused it was an ‘endless’ loop. For instance, on the AfterUpdate Event of Control1, it changes the value of Control2. Control2 has an AfterUpdate Event that changes Control1. Now, situations like these can happen from time to time, you just have to put a little ‘checking’ into the process, so that when the last leg of the loop finishes, the first leg knows everything is done, and stops. What is really wierd, when I have seen this occurance, I don’t get an overflow error, or any error for that matter, and the process just stops….all on it’s own. You can tell when it’s done too, cause the screen stops gittering. It’s basically like Access says to itself ‘this is pointless’, and just stops the code (you can keep using other stuff, and the code isn’t interrupted in anyway).

Reply | Quote

mmm….I think that I’ll have to check this one out.

I spoke to someone in the office and they said that there was a macro attached to the AfterUpdate event of one of the controls causing the problem but without knowing what the macro does it’s difficult to assess it.

Next time I’m in….

Thanks

Reply | Quote

The problem I experienced (and I’ll have to admit…I caused it…..hey, when you’re writing code at 2 in the morning…you tend to forget a few details….like stopping an endless loop! ), was all code, no macros. But you can have a Macro ‘run’ another macro, or there could be two macro’s feeding off of each other….it’s still one event firing another…and so on.

Just have them remove one of the AfterUpdate events, to see if that prevents the ‘flicker’. If it does, problem identified (not necessarily solved….). If it’s a macro, they should just be able to ‘cut’ the macro name from the event, try the form, then paste it back in…without affecting anything.

Reply | Quote

I’ll try that tomorrow – thanks.

Meanwhile back to your Intro to ASP page….(and about time I got around to it! )

Reply | Quote

I almost got yelled at for that tutorial, because I posted it as a few large emails on the AccessD Email list. I sure wish I had it when I started using ASP. (Even more so, the VBA tutorial I wrote when I was teaching myself VB/VBA! ).

Reply | Quote

Thanks Drew – the hardest thing about a new area is sometimes the first step. When I think of some of the procedures I’ve created in VBA, having seen your article ASP seems less daunting.

Back on topic tomorrow when I’ve got in touch with the office

Reply | Quote

Okey dokey! I’ll keep my fingers crossed for you, that it’s just an endless loop!

Reply | Quote