"Pulling" Centralized data.mdb
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.
Instructions
- Run Pull_down_centralized_data.vbs
- Template:Discussion where on the collector's PC is this? Ttenbergen 21:01, 2014 September 29 (CDT)
- 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 of the day, it should ALWAYS be in the 'push' mode.
Deadline for collectors to send is Thursday at 1pm.
When you 'pull'
centralized.mdb
and phi.mdb
It goes into the desktop centralized_on_c (folder icon)
from the RegionalWRHA (wreath icon)
Pull mode is for the data processor to do edits, etc.
Push mode is for everyone else to see the data
** Before backing up, and going home ALWAYS make sure you are in the 'push' mode
The Basic Steps
1) Pull data - deadline to send is Thurs 1pm
2) See who Sent
this is where the data processor does a quick check for discrepencies in site, location, etc
3) Open Front End
4) Perform 'NDC Queries' to correct and clean data
steps are covered in Check For Problems below
5) Push data back
STEPS TO PULL
When in the Pull mode, data processor can edit, but not perform a Back Up
Can only Back Up while in the Push mode
Go to 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
Srusnak 13:57, 2014 July 31 (CDT)