Possible issue with Access 2007

[bknight]

I have an interesting minor issue with Access 2007, many times during the day the record/field that is in focus begins to oscillate between the value in the field and null/blank. This may go on for maybe ten seconds and then stop at value not null. Anyone heard of this?

[HansV]

Is that in a table, in a query, on a form, on a report?

[bknight]

They are all forms.

[HansV]

Perhaps the value is being recalculated many times in quick succession...

[George Hepworth]

Another possibility is that you have a timer event on that form that is triggering some action.

Still another is that the form is corrupted.

Still another is that there is some flakiness in your network connection where the BE is stored.

But given the fact that 2007 is now 18 years old and long, long out of support, it's highly unlikely there would be any fix for a problem if it something has gone wrong in your installation.

You could try repairing or reinstalling your current Access 2007 instance, though.

[bknight]

Another possibility is that you have a timer event on that form that is triggering some action.

No timer event, just a straight presentation of a table.

Still another is that the form is corrupted.

Possible with all that I had had to deal with since the op sys was renewed.

Still another is that there is some flakiness in your network connection where the BE is stored.

I don't think this is applicable, since everything is on the hard drive, no cloud linking on any Db I have.

But given the fact that 2007 is now 18 years old and long, long out of support, it's highly unlikely there would be any fix for a problem if it something has gone wrong in your installation.

while this is true, it also has the history to discover/fix related issues.

You could try repairing or reinstalling your current Access 2007 instance, though.

I hadn't thought of that one, so after everything is shut down, I'll give this a try. Mind you The data doesn't change with this on/null cycle, just annoying as the Db is "frozen" during this flashing/changing, once it stops everything is good to go.
Thanks
ETA: this issue is not very repetitive, nor is it consistent sometimes it will occur since the Db is running all the time, it occurs when just idle, it occurs while entering data and it occurs across many if not all my Dbs, although I am unable to say it occurs on all, just a possibility.

[George Hepworth]

The point made about Access 2007 being out of support is precisely that Microsoft will notfix any new issues that surface in it any longer.

That said, your comment about the seeming randomness of the appearance of the problem suggests to me more than ever that it's either in the network or in the installation of Access itself. "...it occurs across many if not all my Dbs ..."

If it were limited to one form in one database, I'd lean more towards a problem in that form.

[bknight]

Well I repaired the office suite and that didn't help. So I deleted the from that was the most used and demonstrated the most errors( although there may have been others, I didn't write any down so that is just a suspicion. I did delete and rebuild the offending form(only this one as I wasn't 100% sure which if any were symptomatic). The report card is in as of today, the "new" form demonstrates the same oscillations from null/blank to a value after all this work, the fields that "flashed", date/time, amount and dividend. When this occurs the pc "locks" up until the flashing/oscillating ends.
Thanks for your suggestions, but none worked. Remember that this software and Db are all on the HD nothing is over the net and no fields are calculated, all are values.

[George Hepworth]

The remaining possibilities lean heavily towards some sort of form refreshing or recalculation of values going on. One possibility could be a timer event. Another could be conditional formatting of controls. A third would be a long-running query or a recordset that is being created in VBA are also potential reasons. None of those things can be validated from a distance.

The best way to get validation might be to share a copy of the accdb so others can go through and review it. Perhaps someone can spot a potential issue. Can you share a copy?

[bknight]

This is a form with a table as record set, all values no calculations. No timer., no refreshening until I hit a refresh button. The only formatting is different records have alternating backgrounds. The Db is 14Meg, so not transferable here and I won't send a coy to anyone, and I don't have a cloud sharing account finally there is account information in the Db, so not sharing the Db.

[Gasman]

You can always obfuscate the data. It is not rocket science.
https://www.accessforums.net/showthread ... ndomize#19

[George Hepworth]

Unfortunately, these circumstances mean we're not going to be able to offer more concrete suggestions. Whatever is going on is internal to your accdb.

[bknight]

You can always obfuscate the data. It is not rocket science.
https://www.accessforums.net/showthread ... ndomize#19

Unfortunately I haven't obfuscated anything just don't desire to publish personal account information on an open source. Quit asking.
That being said I took your suggestion and deleted all records prior to this year and zipped the remainder but alas the file is too large, sorry.
George I know, but thanks anyway.

[bknight]

I compacted the Db and zipped it and it is ok to post.
Have at it guys.

[HansV]

Does the problem occur in this version of the database for you?

I tested the frmEnterTransactions and Trades forms in Access in Microsoft 365. I moved from record to record, and scrolled down/up and right/left quite a bit. At no time did I see a text box oscillating between a value and a blank.

I'm curious to hear what others experience.

I did notice one error on the Trades form: the control source of one text box is Qtyeft instead of QtyLeft, so it showed #Name?
Once I corrected that, the text box displayed a value.

[bknight]

Does the problem occur in this version of the database for you?

I tested the frmEnterTransactions and Trades forms in Access in Microsoft 365. I moved from record to record, and scrolled down/up and right/left quite a bit. At no time did I see a text box oscillating between a value and a blank.

I'm curious to hear what others experience.

I did notice one error on the Trades form: the control source of one text box is Qtyeft instead of QtyLeft, so it showed #Name?
Once I corrected that, the text box displayed a value.

There may be no oscillating perhaps due to memory issues, but that is only IMO. Know and I have forgotten to change it. Thanks
Almost 8K records were deleted in the test Db.

ETA: Whcih control was that error? I did correct it in the frmEnterTranasactions

[HansV]

The text box is named Qtyeft

[Gasman]

Unfortunately I haven't obfuscated anything just don't desire to publish personal account information on an open source. Quit asking.

I was not asking , just giving you an option to load the db with private information hidden.

[George Hepworth]

The only thing I can see that might reflect the fluctuation would be what happens when the form called "frmEnterTransactions" opens.
You open several other forms in succession in that Forms Open event. That does cause my screen to flicker as each one is opened.

Private Sub Form_Open(Cancel As Integer)
DoCmd.SelectObject acTable, , True
DoCmd.Minimize
DoCmd.MoveSize 140, 2556, 20980, 6820 'Left Top width Height
DoCmd.OpenForm ("frmOpenPositionsFirst"), view:=acFormDS
DoCmd.OpenForm ("frmDividends"), view:=acFormDS
DoCmd.OpenForm ("frmDivByMonth"), view:=acFormDS
DoCmd.OpenForm ("frmDivByMonth_Previous_Year"), view:=acFormDS
DoCmd.OpenForm ("frmDailyprof"), view:=acFormDS
DoCmd.OpenForm ("frmWeekProf"), view:=acFormDS
DoCmd.OpenForm ("frmMonthProf"), view:=acFormDS
DoCmd.OpenForm ("frmRefreshButton"), view:=acNormal
Me.SetFocus
Me.Type.SetFocus
End Sub

When each of those forms opens, it may be running additional code on the Open or Load or Current events of those additional forms. If each additional form is working with large recordsets, it could be related to the flickering that reflects those additional events. I don't see it as fluctuations in any particular form, just the overall screen activity so that is just a guess.

To verify or disprove this possibility, can you comment out those form loads and see if that resolves the issue?

ALSO, and this is important here and in all your databases. You need to add Option Explicit to each module.

https://learn.microsoft.com/en-us/offic ... -statement

[bknight]

The oscillations occur well after all the forms are open, so that isn't it, besides there are no calculations in any of the queries/forms aside from what calculations are required to group or sum. I you look at some of the queries there are a few calculations on static field data these and the rest of query calculations should be finished calculating when the Db opens, feeding the forms. Anyway the flickering occurs about anytime after the Db is open