I am very impressed with the suite since purchasing three seats this past week.
However I am not sure the best way to integrate all the means available to keep it all up-to-date.
I wrote a project in AMS that is a document launcher. Users have it on a USB thumb drive and when run it needs to be able to check/update any of the 200 or so .pdf and .doc files that it launches. This way the users (who *must* always have the most recent versions of the regulations on the thumb drive) will have a truly hands-off way to always have the most current docs.
I use a freeware program called updateXpress to check AMS's "docs" folder and automatically update any file that is newer on the server. It's a slick way to update these individual files, but I would like to use TU and VP to do the same.
Here's my dilemma: I like that VP makes it very simple to do updates, but since I might update a file here and there daily, it would require daily versions and subsequent backups of each day's version--since each version requires that day's build be maintained in a separate directory.
TU seems good for this, however, it's more manually intensive and I need to pass off the maintenance of this program to luddites who need it to be VERY simple.
I am interested in getting some ideas on how to leverage the $3000 we just spent on the suite and make the boss happy, and avoid the project crashing when I get promoted/move/etc. There will be 1500 users of this project and the accuracy of the product needs to be 100%, as it's aviation safety-of-flight related.
Also, can I use VP to do updates of the actual AMS program, and TU to do updates of individual files?
Lots of words, but thanks for your attention/help everyone!
-John Van Huffel
However I am not sure the best way to integrate all the means available to keep it all up-to-date.
I wrote a project in AMS that is a document launcher. Users have it on a USB thumb drive and when run it needs to be able to check/update any of the 200 or so .pdf and .doc files that it launches. This way the users (who *must* always have the most recent versions of the regulations on the thumb drive) will have a truly hands-off way to always have the most current docs.
I use a freeware program called updateXpress to check AMS's "docs" folder and automatically update any file that is newer on the server. It's a slick way to update these individual files, but I would like to use TU and VP to do the same.
Here's my dilemma: I like that VP makes it very simple to do updates, but since I might update a file here and there daily, it would require daily versions and subsequent backups of each day's version--since each version requires that day's build be maintained in a separate directory.
TU seems good for this, however, it's more manually intensive and I need to pass off the maintenance of this program to luddites who need it to be VERY simple.
I am interested in getting some ideas on how to leverage the $3000 we just spent on the suite and make the boss happy, and avoid the project crashing when I get promoted/move/etc. There will be 1500 users of this project and the accuracy of the product needs to be 100%, as it's aviation safety-of-flight related.
Also, can I use VP to do updates of the actual AMS program, and TU to do updates of individual files?
Lots of words, but thanks for your attention/help everyone!
-John Van Huffel
Comment