PHI copy automation: Difference between revisions

m interlinking
Line 7: Line 7:
It copies the PHI files exported by [[CCMDB.mdb]] during [[sending]] to {{Regionalserver|Output\_PHI}} to  X:\CCMDB\PHI. Then it calls the script [[Load Data.vbs]].
It copies the PHI files exported by [[CCMDB.mdb]] during [[sending]] to {{Regionalserver|Output\_PHI}} to  X:\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 X:\CCMDB\PHI\PHI Archive\ to prevent duplicate processing.
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 X:\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 [[User:Bcloutier|Bcloutier]] 19:47, 2013 November 20 (CST)
'''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 [[User:Bcloutier|Bcloutier]] 19:47, 2013 November 20 (CST)
Line 18: Line 18:
* computer is rebooted and network connection to X is checked to see if it has been re established, otherwise this bat files is not able to do its job.   
* computer is rebooted and network connection to X is checked to see if it has been re established, otherwise this bat files is not able to do its job.   
**occurrence: Monday June 15.14 at 1700 hrs and all day June 16.14: issue: Castrophic hardware failure on this network drive had occurred.  
**occurrence: Monday June 15.14 at 1700 hrs and all day June 16.14: issue: Castrophic hardware failure on this network drive had occurred.  
== Related Articles ==
{{Related Articles}}