Possible issue with Access 2007

[George Hepworth]

I take it that you didn't try my suggested testing method?

"...look at some of the queries..."

Can you help someone help you by identifying those queries to which you refer?

BTW: queries run when an event triggers them to run. None of them could be finished calculating when the db opens. They can only start to run when a form for which they provide records is opened. Or when something in your code triggers them to run.

But, inasmuch as you indicate that the flickering is random, and I can't see that happening in this sample, I'm not able to offer more ideas at the moment.

[bknight]

Each form other than EnterTransactions is driven by a query. And they are opened when the Db is opened. If you refer to commenting out form openings, no I didn't. I doubt that I will each is a snapshot of the account. This behavior was not observed prior to the op sys refresh I did a month or so ago. The Db has been used for over ten years with EnterTransactions, Openfirst, Dividend, Divbymonth, Prevyeardivbymonth have been around since the beginning with the weeklyprofit monthprofit added last month. Those would be perhaps a suspect. I suppose I'll close them next week and see if that solves the problem.

[George Hepworth]

If you refuse to attempt possible trouble-shooting attempts, how will you know, not just assume, it is not relevant?

True, it's not likely it will matter. The reason you try things is to rule out possibilities.

It may be a matter of having reached a critical number of records in one or more of the tables being queried. That's not unheard of with long-term database applications, by the way.

You mention an "op sys" refresh. What does that include?

Also, is it a coincidence that "...with the weeklyprofit monthprofit added last month" also happened about the same time of that "op sys" refresh when the problem was first observed?

Again, the whole point of trouble-shooting is to try to demonstrate whether a problem is caused or not caused by some factor.

It's equally important to rule things out, not just ignore them because we think they should not be relevant. Prove they are not. And then move on.

[bknight]

For the last two days I have close down three forms frmMothprof, frmWeeklyprof and frmDaily prof. Yesterday I didn't observe and "flickering", however today I did notice a flickering in the field Symbol. This flickering didn't last very long, maybe .5 sec to 1 second, in relation to what was occurring last week. There are currently four forms open. frmOpenPosistionsFirst which is based on three queries(uinion and two others), frmDivByMonth which has a grouping query, frmDivByMonth_Prev_year which also has a grouping query and the main form, frmEnterTransactions which has a table as record set nothing fancy about this form. Anyone that downloaded the Db could have realized that with a bit of prying/review.
By op sys refresh, The op sys Win10, was reinstalled wiping put all previous data on the HD and all programs has had to be reinstalled.

[George Hepworth]

That does suggest the problem has to do with multiple forms being opened and left to refresh their recordsets, which they do. And, as the number of records in those recordsets grow over time, that load increases slowly over time.

Thank you for explaining what "op sys refresh" means in your organization.

==========================
"Anyone that downloaded the Db could have realized that with a bit of prying/review."

And as a final note, taking a back-handed swipe at people trying to offer ideas and suggestions is not the best way to encourage future responses.

I will take that comment into consideration when reviewing any future posts here.

[bknight]

I guess I don't understand the working of Access. Theses are all static numbers except when new records are added. What drives the form to refresh just sitting idle. There are no added timers, now there may imbedded timers that Access adds. Infact the fields don't change values unless new forms are added/changed/refreshed/reloaded.

[bknight]

From Refresh or requery data:

The refresh process updates the existing data in a datasheet or form, and doesn’t reorder records, display new records, or remove any deleted records or records that no longer meet specified criteria.

This answered my question. George, you were/are correct there is a timer function built into the application.

[HansV]

Yes, a timer event procedure is a likely cause of flickering. You earlier wrote "No timer event"...

[bknight]

Yes, a timer event procedure is a likely cause of flickering. You earlier wrote "No timer event"...

Meaning that I had not coded a timer in the Db and I didn't know that Access has a built-in timer. Now I know that the timer exists.