1 of 1 people found this helpful
No, FMS is not a client so it cannot access another FMSs files.
We use robot computers in this scenario. The robot is running a special file that has a series of records to schedule when each script is to run.
The scheduling file is very complex as it supports multiple robots running scripts at either an interval or time of day or both.
Scripts are written in such a way so overlapping scripts don't interfere with each other.
Thank you for the reply. I have a robot but it is already pretty busy and I thought I had set it up about 8 years ago because of importing/exporting on fms was complicated but it was probably originally for this reason too as the solution is split across 3 servers. I will try and find some gaps in between all the other schedules to add this new one in. Every now and again I think I must review things and see if I still need robot but it appears there are still a few valid reasons for having it. Thank you for confirming that the subscript would not perform for this reason - I did a quick google and look at help but had not found anything to say that this was definitely a caveat but had a sense this was not the first time I had failed to make this work. I appreciate your time.
I think 24U or Troi have plugins with functions to work with other computers but don't know if they will work with different servers. You might ask.