PHI copy automation: Difference between revisions
Ttenbergen (talk | contribs) m Text replacement - "Transition to Database Server" to "Re-platforming" |
Ttenbergen (talk | contribs) m Text replacement - "X:\" to "{{S:\MED\CCMED}}" |
||
| Line 11: | Line 11: | ||
Every 60 minutes it runs the batch file [[Copy PHI.bat]]. | Every 60 minutes it runs the batch file [[Copy PHI.bat]]. | ||
It copies the PHI files exported by [[CCMDB.accdb]] during [[sending]] to {{Regionalserver|Output\_PHI}} to | It copies the PHI files exported by [[CCMDB.accdb]] during [[sending]] to {{Regionalserver|Output\_PHI}} to {{S:\MED\CCMED}}CCMDB\PHI. Then it calls the script [[Load Data.vbs]]. | ||
The script [[Load Data.vbs]] accesses [[PHI Loader.accdb]] and runs the sub ''loadAllCSVFiles'', which calls the code that imports all csv files found within the directory. The csv loading code also moves the files again into an archive folder | The script [[Load Data.vbs]] accesses [[PHI Loader.accdb]] and runs the sub ''loadAllCSVFiles'', which calls the code that imports all csv files found within the directory. The csv loading code also moves the files again into an archive folder {{S:\MED\CCMED}}CCMDB\PHI\PHI Archive\ to prevent duplicate processing. See [[Automatic updating of MS Access Databases using scheduled tasks]] for more info on how this works. | ||
'''If the task runs and there are no problems the task will list "0x0" in the last results column. Any other code would require review.''' - This needs to be reviewed as the last line of the batch file has changed the the return value may be altered | '''If the task runs and there are no problems the task will list "0x0" in the last results column. Any other code would require review.''' - This needs to be reviewed as the last line of the batch file has changed the the return value may be altered | ||