hexagon logo

Scripts on network

We have a few scripts that we use and I have a database of the scrips on each computer. Would there be an issue if I put the scrips on a shared network drive and had the programs recall them from there?

This question arises because all of our computers have the same username so the path is the same (C:Users/INSP/Desktop/Scripts). We recently got a new computer and the username is different so the path is broken. If the database was on the network, the path would then be the same for all the computers. There would obviously be issues if the network was down but the scripts we use run at the end of the program and we would only have to do a few extra steps if the scripts don't run and would not effect the actual measurement routine.
Parents
  • We run shared .BAS and .EXE automation stored on a shared network drive about 100, maybe 150 times a day between a few dozen CMMs and some offline seats. Seems to have been working OK for the past decade.

    Tips:
    Backup, backup, and backup the backups.

    Have local copies of the scripts stored on the hard drive of each machine, with an identical folder structure except the network drive letter vs. the local drive letter. This is a fallback for when the network goes down, then you can run a program after editing just the drive letters in the script call paths.

    Make sure someone else knows how to troubleshoot scripts - and these scripts should be well documented with comments throughout them.

    If you use EXEs, always keep copies of the source files (which also require comment documentation!) in the backups. I have seen some brilliant automation get lost to history once the old PC-DMIS 3.7 and Windows XP computers went away, because nobody could edit the source code and make it work with new versions of Windows & PC-DMIS.
Reply
  • We run shared .BAS and .EXE automation stored on a shared network drive about 100, maybe 150 times a day between a few dozen CMMs and some offline seats. Seems to have been working OK for the past decade.

    Tips:
    Backup, backup, and backup the backups.

    Have local copies of the scripts stored on the hard drive of each machine, with an identical folder structure except the network drive letter vs. the local drive letter. This is a fallback for when the network goes down, then you can run a program after editing just the drive letters in the script call paths.

    Make sure someone else knows how to troubleshoot scripts - and these scripts should be well documented with comments throughout them.

    If you use EXEs, always keep copies of the source files (which also require comment documentation!) in the backups. I have seen some brilliant automation get lost to history once the old PC-DMIS 3.7 and Windows XP computers went away, because nobody could edit the source code and make it work with new versions of Windows & PC-DMIS.
Children