Forms looks like its looping...

[darrent]

Hello

I have a form, with 3 subforms, attached to an activex scrollbar.

This has been working fine, but I have now tried to add another field to one of the forms, and when the form is displayed, it looks like its looping, just the first row data being shown, with the rest 'flickering', it can be rectified by moving the mouse pointer over the field, and the problem clears.

This is no problem with the 14 rows I am testing at the moment, but when the db is populated with over 1000 records, then I may have some problems.

I have never seen anything like this on access, and was wondering if I am doing something, or is a known problem.

By the way, I'm using MS Office Access 2003.

thanks

Darren

 

[adam_fleck]

I ran up against something like this too. In an Access 2003 .adp on Windows 2000/Windows XP, one of the applications I'm working on has a form with a 5-page tab control, each tab page having (yikes) a datasheet subform. One page even has a browser too. Oh dear.

Remarkably, all this works well, except when I tried the experiment of using conditional formatting to highlight certain rows in one of the datasheet subforms.

Sometimes, when the user turned to that page, or scrolled it onto a new record, the conditional formatter would go into a loop, and, except for the first row, colours would rush up and down. This usually stopped when the user clicked on the datasheet, though occasionally Access got so obsessed with the loop that everything else locked up.

The only fix I've found so far, is to remove conditional formatting. If you haven't applied conditional formatting, and if the new field you added definitely doesn't have any conditional formatting applied, then this won't help.

There are a few other flicker issues that I'm trying to sort, but I haven't really got anywhere yet. I haven't managed to find much about this on the web. In fact, only this:

In Access 2003/Windows XP, unbound labels cause flicker on tab controls
http://members.iinet.net.au/~allenbrowne/ser-46.html

 

[darrent]

Thanks for the reply, looks like its a similar problem, but I've now found that Microsoft have accepted this as a Bug.

Heres the URL...
http://support.microsoft.com/default.aspx?scid=kb;en-us;555033

Fix option 3 has just worked for me.

Once again thanks.