Do your scripts use global fields?
It does use global fields in a couple of instances, but these fields (2) are Global marker fields.
The first one marks any jobs i want picked with a unique marker number - the script does copy this marker into a field related to the relevant component and the global marker field then gets cleared.
The next global field is another marker type field - the Warehouse guys enter in the global marker number into thier RF gun and it looks up the components that need to be picked.
The first componet shows up on thier portal - the guys scan the location and click the "next" button which triggers the scrpit which moves stock form the warehouse into production, works out how much of the same stock renmains to be picked, recaluclates and re-freshes the picklist.
It's at this point the script seems to start freaking out (it seems to not beable to find the components it's supposed to and throws random components into the list.
The script does use the global field to find related components again.
Again, it all works fine on my machine and works intermittently on other machines but more often than not - other machines freak out.
Are you aware of how Global fields function differently from client machines as apposed to how they function from a single user machine or the host? This is the most common cause of scripts behaving differently once the system is hosted over a network.
If that's not the cause of your trouble here, we'd need to see the actual scripts in order to be able to suggest a reason for your troubles.
- You can upload a screen shot by clicking the edit link to your original message and uploading it there
- You can upload a screen shot to a file share site and post the download link to a new response you post here.
- You can print a script to a PDF, open the PDF and then select and copy the script as text from the opened PDF.
- If You have FileMaker advanced, you can generate a database design report and copy the script as text from there.