7 Replies Latest reply on Jul 27, 2009 5:09 PM by kmtenor

    FM Pro Advanced 10 Bug Active X Automation DoFMScript not Working with parameters

    smower

      Summary

      FM Pro Advanced 10 Bug Active X Automation DoFMScript not Working with parameters

      Description of the issue

      FM Pro Advanced 10 Windows XP Professional The DoFMScript function in Active X automation is not working with script parameters FMProDoc.DoFMScript ("MyScript", "parameter") is giving errors: Compile Error Expected: =  so that we can not send parameters to the script.

        • 1. Re: FM Pro Advanced 10 Bug Active X Automation DoFMScript not Working with parameters
          TSGal

          smower:

           

          Thank you for your post.

           

          I have forwarded this information to our Development and Software Quality Assurance (Testing) departments so they can be aware of this issue.

           

          TSGal

          FileMaker, Inc. 

          • 2. Re: FM Pro Advanced 10 Bug Active X Automation DoFMScript not Working with parameters
            kmtenor
              

            Is there any update as to whether this is fixed or not?  We have tried it with our own script, and are actually getting an error from the VBScript engine with FMPA10.0v1 on Vista Business.

             

             Error:     Wrong number of arguments or invalid property assignment: 'dofmscript'

             Code:     800A01C2

             Source:  Microsoft VBScript compilation error

             

             

            Also, is there any reference anywhere as to what calls are possible from the Active X automation?  We have looked around online, but not found much that is definitive.

             

            Thanks.

             

            -Kevin

            • 3. Re: FM Pro Advanced 10 Bug Active X Automation DoFMScript not Working with parameters
              TSGal

              kmtenor:

               

              Thank you for your post.

               

              Our Development and Software Quality Assurance (Testing) departments confirm that a parameter cannot be passed to DoFMScript.  However, no other information is available.

               

              TSGal

              FileMaker, Inc. 

              • 4. Re: FM Pro Advanced 10 Bug Active X Automation DoFMScript not Working with parameters
                kmtenor
                  

                Thanks for your quick reply, TSGal.  If you could add a request for the ability to pass a script parameter via DoFMScript to a future release, that would be a huge help to us!

                 

                Thanks again.

                 

                -Kevin

                • 5. Re: FM Pro Advanced 10 Bug Active X Automation DoFMScript not Working with parameters
                  TSGal

                  kmtenor:

                   

                  The request to pass a script parameter was originally proposed when this was initially reported.

                   

                  TSGal

                  FileMaker, Inc. 

                  • 6. Re: FM Pro Advanced 10 Bug Active X Automation DoFMScript not Working with parameters
                    jaynelson2112
                      

                    kmtenor, I have written scripts in Python on Windows and use ActiveX/COM to automate Filemaker quite frequently, the most definitive reference I could find was this:

                     

                    http://www.filemaker.com/help/html/create_script.12.11.html

                     

                    According to this documentation, DoFMScript only accepts one parameter, the name of the Filemaker script to run.

                     

                    To pass parameters to a Filemaker script, save the parameters into a tab-delimited or comma-delimited text file and then import that file into a table in Filemaker.

                     

                     

                    • 7. Re: FM Pro Advanced 10 Bug Active X Automation DoFMScript not Working with parameters
                      kmtenor
                        

                      <!--  /* Font Definitions */ @font-face      {font-family:&quot;Cambria Math&quot;;      panose-1:2 4 5 3 5 4 6 3 2 4;      mso-font-charset:1;      mso-generic-font-family:roman;      mso-font-format:other;      mso-font-pitch:variable;      mso-font-signature:0 0 0 0 0 0;} @font-face      {font-family:Calibri;      panose-1:2 15 5 2 2 2 4 3 2 4;      mso-font-charset:0;      mso-generic-font-family:swiss;      mso-font-pitch:variable;      mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal      {mso-style-unhide:no;      mso-style-qformat:yes;      mso-style-parent:&quot;&quot;;      margin:0in;      margin-bottom:.0001pt;      mso-pagination:widow-orphan;      font-size:12.0pt;      font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;      mso-fareast-font-family:Calibri;      mso-fareast-theme-font:minor-latin;} .MsoChpDefault      {mso-style-type:export-only;      mso-default-props:yes;      font-size:10.0pt;      mso-ansi-font-size:10.0pt;      mso-bidi-font-size:10.0pt;} @page Section1      {size:8.5in 11.0in;      margin:1.0in 1.0in 1.0in 1.0in;      mso-header-margin:.5in;      mso-footer-margin:.5in;      mso-paper-source:0;} div.Section1      {page:Section1;}   --><!--  [if gte mso 10]&gt; &lt;style&gt; /* Style Definitions */ table.MsoNormalTable      {mso-style-name:&quot;Table Normal&quot;;      mso-tstyle-rowband-size:0;      mso-tstyle-colband-size:0;      mso-style-noshow:yes;      mso-style-priority:99;      mso-style-qformat:yes;      mso-style-parent:&quot;&quot;;      mso-padding-alt:0in 5.4pt 0in 5.4pt;      mso-para-margin:0in;      mso-para-margin-bottom:.0001pt;      mso-pagination:widow-orphan;      font-size:11.0pt;      font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;      mso-ascii-font-family:Calibri;      mso-ascii-theme-font:minor-latin;      mso-fareast-font-family:&quot;Times New Roman&quot;;      mso-fareast-theme-font:minor-fareast;      mso-hansi-font-family:Calibri;      mso-hansi-theme-font:minor-latin;      mso-bidi-font-family:&quot;Times New Roman&quot;;      mso-bidi-theme-font:minor-bidi;} &lt;/style&gt; &lt;![endif]  -->jaynelson2112:

                       

                      Thanks for that reference.  It's a huge help to get us to where we want to go.  Can't believe we couldn't find it on the filemaker site ourselves!

                       

                      We started heading toward the file import solution as soon as we heard there was no parameter available in the ActiveX call.  Our other thought was to write to the hosted database from the os-level script via ODBC/DSN, and use the machine name and/or user logon as well as a timestamp to key the information.  We'll post in a new thread what we finally settle on, if for no other reason than to make the information searchable the way we went looking for it!

                       

                      Thanks again.

                       

                      -Kevin