Cross Check Engine: Difference between revisions

(One intermediate revision by the same user not shown)

Line 1:

This are just some notes re how I might re-write how [[CCMDB.accdb]] runs the cross checks. See also [[Problems related to event timing of data consistency checks]]

This are just some notes re how I might re-write how [[CCMDB.accdb]] runs the [[cross check]]s. It is a long-term goal to do this, but it’s not trivial to implement and would require re-building the way we do cross-checks, which would take several days and likely lead to other disruptions.

See also [[Problems related to event timing of data consistency checks]] and [[CCMDB.accdb flickers or flashes]].

=== Definition/Data structure ===

Line 5:

Line 7:

** fields: Error msg string, wiki URL, query name, soft/hard check, complete/incomplete, start_DtTm, end_DtTm

* table CCE_Fields

** fields: database field name, form field name, associated checkbox (can there ever be more than one?), tmpField (YN) (Need to be able to do cross ~~checks~~ on tmp entries, but they need to work totally differenty in terms of how they are triggered)

** fields: database field name, form field name, associated checkbox (can there ever be more than one?), tmpField (YN) (Need to be able to do [[cross check]]s on tmp entries, but they need to work totally differenty in terms of how they are triggered)

* table CCE_FieldChecks

** relates CCE_Fields to CCE_CrossChecks

Line 32:

Line 34:

* Is it possible to leave that window open and let the user figure out the problem? OR does it need to close? I think turning it not modal would allow moving back and forth.

** If it stays open, what should happen if the user edits a field or checks a checkbox while still open? No good answer, so should stay modal.

=== Other thoughts ===

@@ Line 1: / Line 1: @@
-This are just some notes re how I might re-write how [[CCMDB.accdb]] runs the cross checks. See also [[Problems related to event timing of data consistency checks]]
+This are just some notes re how I might re-write how [[CCMDB.accdb]] runs the [[cross check]]s. It is a long-term goal to do this, but it’s not trivial to implement and would require re-building the way we do cross-checks, which would take several days and likely lead to other disruptions.
+See also [[Problems related to event timing of data consistency checks]] and [[CCMDB.accdb flickers or flashes]].
 === Definition/Data structure ===
@@ Line 5: / Line 7: @@
 ** fields: Error msg string, wiki URL, query name, soft/hard check, complete/incomplete, start_DtTm, end_DtTm
 * table CCE_Fields
-** fields: database field name, form field name, associated checkbox (can there ever be more than one?), tmpField (YN) (Need to be able to do cross checks on tmp entries, but they need to work totally differenty in terms of how they are triggered)
+** fields: database field name, form field name, associated checkbox (can there ever be more than one?), tmpField (YN) (Need to be able to do [[cross check]]s on tmp entries, but they need to work totally differenty in terms of how they are triggered)
 * table CCE_FieldChecks
 ** relates CCE_Fields to CCE_CrossChecks
@@ Line 32: / Line 34: @@
 * Is it possible to leave that window open and let the user figure out the problem? OR does it need to close? I think turning it not modal would allow moving back and forth.
 ** If it stays open, what should happen if the user edits a field or checks a checkbox while still open? No good answer, so should stay modal.
 === Other thoughts ===