CCMDB.accdb flickers or flashes: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) Created page with "{{Bug}} If this happens when you first open a record, or as you close it, then it’s because of all the cross checks we run. There are a bunch of screen re-freshes in the process, because some checks can run at different times and we need to make sure the screen is refreshed at least once. I have a long-term goal to change how we do the cross checks, they have sort of grown as we have built the program and have not been re-factored in over 10 years." |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
{{Bug}} | {{Bug}} | ||
If this happens when you first open a record, or as you close it, then it’s because of all the cross checks we run. There are a bunch of screen re-freshes in the process, because some checks can run at different times and we need to make sure the screen is refreshed at least once. I have a long-term goal to change how we do the cross checks, they have sort of grown as we have built the program and have not been re-factored in over 10 years. | If this happens when you first open a record, or as you close it, then it’s because of all the cross checks we run. There are a bunch of screen re-freshes in the process, because some checks can run at different times and we need to make sure the screen is refreshed at least once. I have a long-term goal to change how we do the cross checks, they have sort of grown as we have built the program and have not been re-factored in over 10 years. | ||
This is related to [[Problems related to event timing of data consistency checks]] and would be addressed by [[Cross Check Engine]]. | |||
== Related articles == | |||
{{Related Articles}} | |||
Revision as of 13:28, 2022 November 29
If this happens when you first open a record, or as you close it, then it’s because of all the cross checks we run. There are a bunch of screen re-freshes in the process, because some checks can run at different times and we need to make sure the screen is refreshed at least once. I have a long-term goal to change how we do the cross checks, they have sort of grown as we have built the program and have not been re-factored in over 10 years.
This is related to Problems related to event timing of data consistency checks and would be addressed by Cross Check Engine.
Related articles
| Related articles: |