Centralized data front end.accdb Change Request: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) m we talked about this; since Pagasa should be able to edit anything including old data following different rules it would be very hard to make cross-checks for her. Could not just re-use collector ones since they only apply to current. So, likely not worth |
Ttenbergen (talk | contribs) m added moving linked pairs |
||
| Line 3: | Line 3: | ||
This article contains requested changes for [[Centralized data front end.mdb]]. See [[Centralized data front end.mdb Change Log]] for it's change log. | This article contains requested changes for [[Centralized data front end.mdb]]. See [[Centralized data front end.mdb Change Log]] for it's change log. | ||
== | |||
=== Move Linked Pairs === | |||
As discussed with Julie to prevent her having to rerun it and to insure that what Pagasa queries against is same as what Julie uses. | |||
* need to change the query and process from one that re-does all, every time, to one that only updates new. | |||
** How will that work for individual older records that were edited? | |||
== See also == | |||
* [[Questioning data back to collectors]] | * [[Questioning data back to collectors]] | ||
* revisit [[! Automated Data Integrity Checks]] | * revisit [[! Automated Data Integrity Checks]] | ||
Revision as of 12:50, 6 June 2017
see the Development Documentation Category for other development logs
This article contains requested changes for Centralized data front end.mdb. See Centralized data front end.mdb Change Log for it's change log.
Move Linked Pairs
As discussed with Julie to prevent her having to rerun it and to insure that what Pagasa queries against is same as what Julie uses.
- need to change the query and process from one that re-does all, every time, to one that only updates new.
- How will that work for individual older records that were edited?