"Pulling" Centralized data.mdb: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) Created page with "This article describes how the Data Processor "pulls down" (ie moves to her local c:\ drive) Centralized_data.mdb for editing. The file gets moved to local because it'..." |
Ttenbergen (talk | contribs) update and some questions |
||
| Line 1: | Line 1: | ||
This article describes how the [[Data Processor]] "pulls down" (ie moves to her local c:\ drive) [[Centralized_data.mdb]] for editing. The file gets moved to local because it's faster there and because it prevents collectors from sending in the middle of update actions. | This article describes how the [[Data Processor]] "pulls down" (ie moves to her local c:\ drive) [[Centralized_data.mdb]] and [[PHI.mdb]] for editing. The file gets moved to local because it's faster there and because it prevents collectors from sending in the middle of update actions. | ||
Data should not be pulled during '''[[designated sending times]]'''. | |||
'''**''' Before going home '''ALWAYS''' make sure you are in the 'push' mode | |||
== Instructions / Steps to Pull == | |||
* double-click on ''Centralized_CCMDB'' (folder shortcut icon) | |||
* double click on [[Pull_down_centralized_data.vbs]] | |||
* Prompts ''do you want to ...'' | |||
* Answer Yes | |||
* Wait for the program to ''pull'' 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. | *The [[Push/Pull log]] will show whether you are in 'push' or 'pull' mode. | ||
== Background == | == Background == | ||
The data processor takes control of the data by " | The data processor takes control of the data by [["Pulling" Centralized data.mdb]], and releases it back for [[sending]] or for others to access by [["Pushing" Centralized data.mdb]]. | ||
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 the 'push' mode. | |||
===can't back up in pull mode? === | |||
=== | |||
When in the ''Pull'' mode, data processor can edit, but not perform a ''Back Up'' | When in the ''Pull'' mode, data processor can edit, but not perform a ''Back Up'' | ||
* {{discussion}} what is this back up and why can it not be done while in pull state? Ttenbergen 21:21, 2014 September 29 (CDT) | |||
Can only Back Up while in the ''Push'' mode | Can only Back Up while in the ''Push'' mode | ||
[[Category:Data Processing]] | [[Category:Data Processing]] | ||
Revision as of 20:21, 2014 September 29
This article describes how the Data Processor "pulls down" (ie moves to her local c:\ drive) Centralized_data.mdb and PHI.mdb for editing. The file gets moved to local because it's faster there and because it prevents collectors from sending in the middle of update actions.
Data should not be pulled during designated sending times.
** Before going home ALWAYS make sure you are in the 'push' mode
Instructions / Steps to Pull
- double-click on Centralized_CCMDB (folder shortcut icon)
- double click on Pull_down_centralized_data.vbs
- Prompts do you want to ...
- Answer Yes
- Wait for the program to pull 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.mdb, and releases it back for sending or for others to access by "Pushing" Centralized data.mdb.
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 the 'push' mode.
can't back up in pull mode?
When in the Pull mode, data processor can edit, but not perform a Back Up
- Template:Discussion what is this back up and why can it not be done while in pull state? Ttenbergen 21:21, 2014 September 29 (CDT)
Can only Back Up while in the Push mode