3 Replies Latest reply on Apr 11, 2011 10:50 AM by philmodjunk

    Problem running scripts on other computers.

    CarlSowden

      Title

      Problem running scripts on other computers.

      Post

      Hi!

      relativley new to filemaker and I am having some problems with the scripts i write (which work fine on my PC running FMP11 advanced) not working on all but one other computer on the server.

      It basically batches up items for our warehouse staff to pick based on quantity and location and guides them round ourwarehouse - needless to say, there are alot of scripts running within scripts, alot of copying from one layout and pasting to another.

      My first thought was that because the computers involved weren't part of the same domain on our network it may be causing the problem - me changed them all to the same domain... no luck.

      then I thought it may be a privialge issue... set all privilages to full access... still no luck.

      Now I'm wondering if my script may be to complex; as it copys and pastes alot of data across several tables and layouts.... i've tried usinf setfield in my scripts instead of copy/paste but it doesn't seen to work (leaves fields blank)

      rather than re-write all my scripts or start from scratch again... I was wondering if anyone might be aware of why these other machines may be operating differently? all the operating systems are the same and they all run off the same server.

      Any advice or insight would be much appreciated.

      Thanks,

      Carl.

        • 1. Re: Problem running scripts on other computers.
          philmodjunk

          Do your scripts use global fields?

          • 2. Re: Problem running scripts on other computers.
            CarlSowden

            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.

            • 3. Re: Problem running scripts on other computers.
              philmodjunk

              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.

              http://help.filemaker.com/app/answers/detail/a_id/5895/kw/global%20fields%20network

              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.

              1. You can upload a screen shot by clicking the edit link to your original message and uploading it there
              2. You can upload a screen shot to a file share site and post the download link to a new response you post here.
              3. You can print a script to a PDF, open the PDF and then select and copy the script as text from the opened PDF.
              4. If You have FileMaker advanced, you can generate a database design report and copy the script as text from there.