"Pushing" Centralized data.mdb: Difference between revisions
Ttenbergen (talk | contribs) m Text replacement - "Centralized data.mdb" to "Centralized data.accdb" |
Ttenbergen (talk | contribs) m Text replacement - "[["Pushing" Centralized_data.accdb]]" to ""Pushing" Centralized_data.accdb" |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
This article describes how the [[Data Processor]] "pushes up" (ie moves to the server from her local c:\ drive) [[Centralized_data. | This article describes how the [[Data Processor]] "pushes up" (ie moves to the server from her local c:\ drive) [[Centralized_data.accdb]] and [[PHI.mdb]] for editing. The file gets moved to the server because collectors can [[send]] to it there. | ||
Data should always be in a "pushed" state during '''[[designated sending times]]'''. | Data should always be in a "pushed" state during '''[[designated sending times]]'''. | ||
'''ALWAYS'' make sure you finish [["Pushing" | '''ALWAYS'' make sure you finish [["Pushing" Centralized_data.accdb]] before you go home''' or [[Data collector]]s will not be able to [[send]] during the next [[designated sending times]]. | ||
== Instructions / Steps to Push == | == Instructions / Steps to Push == | ||
| Line 18: | Line 18: | ||
== Background == | == Background == | ||
The data processor takes control of the data by [["Pulling" | The data processor takes control of the data by [["Pulling" Centralized_data.accdb]] | ||
, and releases it back for [[sending]] or for others to access by [["Pushing" Centralized_data.accdb]]. | |||
The current state of pushing/pulling can be seen in the [[Push/Pull log]] | The current state of pushing/pulling can be seen in the [[Push/Pull log]] | ||
At the beginning and end of the day, it should '''ALWAYS''' be in [["Pushing" [[ | At the beginning and end of the day, it should '''ALWAYS''' be in [["Pushing" [[Centralized_data.accdb]]|push]] mode. | ||
== Related articles == | == Related articles == | ||
Latest revision as of 15:36, 23 July 2025
This article describes how the Data Processor "pushes up" (ie moves to the server from her local c:\ drive) Centralized_data.accdb and PHI.mdb for editing. The file gets moved to the server because collectors can send to it there.
Data should always be in a "pushed" state during designated sending times.
ALWAYS make sure you finish "Pushing" Centralized_data.accdb before you go home or Data collectors will not be able to send during the next designated sending times.
Instructions / Steps to Push
Make sure to close database!
- double-click on Centralized_CCMDB (folder shortcut icon)
- double click on Push_up_centralized_data.vbs
- Prompts do you want to ...
- Answer Yes
- Wait for the program to push which takes approx. 5 minutes
- Prompts finished processing pull script
- click OK
- The Push/Pull log will show whether you are in 'push' or 'pull' mode.
Background
The data processor takes control of the data by "Pulling" Centralized_data.accdb , and releases it back for sending or for others to access by "Pushing" Centralized_data.accdb.
The current state of pushing/pulling can be seen in the Push/Pull log
At the beginning and end of the day, it should ALWAYS be in [["Pushing" Centralized_data.accdb|push]] mode.
Related articles
| Related articles: |