Jump to content


  • Posts

  • Joined

  • Last visited

FileMaker Experience

  • Skill Level
  • FM Application

Platform Environment

  • OS Platform
  • OS Version
    MacOS Catalina, Windows 10

FileMaker Partner

  • Certification
    Not Certified

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

JamesBand's Achievements


Enthusiast (6/14)

  • First Post
  • Collaborator
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges



  1. If you actually have the Applscript working the way you want, your problem is not really with Applescript. It is a problem with Layouts and Fields. Anyway, I'd setup a text field that can be a space " " or nothing. Then, create a valuelist with a space " ". Then, drop it on the appropriate layout and format it as a checkbox that references the above valuelist. Create a script that only executes the applescript if the above field is empty and after successful execution sets the field to a space " ". Finally, I'd tie the field instance on the layout to the above script. Hope this helps.
  2. OK... I have added some files to the Customer table and updated the FMxsl stylesheet. <?xml version='1.0' encoding='utf-8'?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output version="1.0" encoding="UTF-8" indent="no" method="xml"/> <xsl:template match="/"> <FMPXMLRESULT xmlns="http://www.filemaker.com/fmpxmlresult"> <ERRORCODE>0</ERRORCODE> <PRODUCT BUILD="" NAME="" VERSION=""/> <DATABASE DATEFORMAT="M/d/yyyy" RECORDS="" LAYOUT="" NAME="" TIMEFORMAT="h:mm:ss a"/> <METADATA> <FIELD EMPTYOK="YES" MAXREPEAT="1" NAME="ListID" TYPE="TEXT"/> <FIELD EMPTYOK="YES" MAXREPEAT="1" NAME="Name" TYPE="TEXT"/> <FIELD EMPTYOK="YES" MAXREPEAT="1" NAME="FullName" TYPE="TEXT"/> <FIELD EMPTYOK="YES" MAXREPEAT="1" NAME="BillAddressBlock" TYPE="TEXT"/> <FIELD EMPTYOK="YES" MAXREPEAT="1" NAME="ShipAddressBlock" TYPE="TEXT"/> <FIELD EMPTYOK="YES" MAXREPEAT="1" NAME="Email" TYPE="TEXT"/> <FIELD EMPTYOK="YES" MAXREPEAT="1" NAME="Phone" TYPE="TEXT"/> </METADATA> <RESULTSET FOUND=""> <xsl:for-each select="QBXML/QBXMLMsgsRq/CustomerQueryRs/CustomerRet"> <ROW MODID="" RECORDID=""> <COL> <DATA> <xsl:value-of select="ListID"/> </DATA> </COL> <COL> <DATA> <xsl:value-of select="Name"/> </DATA> </COL> <COL> <DATA> <xsl:value-of select="FullName"/> </DATA> </COL> <COL> <DATA> <xsl:for-each select="BillAddressBlock/*"> <xsl:value-of select="."/> <xsl:text>&#10;</xsl:text> </xsl:for-each> </DATA> </COL> <COL> <DATA> <xsl:for-each select="ShipAddressBlock/*"> <xsl:value-of select="."/> <xsl:text>&#10;</xsl:text> </xsl:for-each> </DATA> </COL> <COL> <DATA> <xsl:value-of select="Email"/> </DATA> </COL> <COL> <DATA> <xsl:value-of select="Phone"/> </DATA> </COL> </ROW> </xsl:for-each> </RESULTSET> </FMPXMLRESULT> </xsl:template> </xsl:stylesheet>
  3. So, I have attached a very ugly proof of concept for Quickbooks 2012 Mac integration with FM 11. Ultimately, I would like to be using something like this to create invoices on my ipod touch and exporting those invoices straight to QB. No extra data entry! Yay! It uses no plugins. It is all done with Global Fields, Applescript (launched from within FM) and Import XML/XSL. At the moment will only pull the customers from an open QB 2012 company file and import them into a table in FM. Be warned, it creates 2 temporary files in the /Users/Shared folder and removes them (assuming the clearFlag is set) when complete. Also, the during the first import, you will have to point to the temporary XML and XSL files. Your mileage may vary. Backup before using. Use at your own risk... yada, yada, yada... QBxml.fp7.zip
  4. Welcome! Is the script that you are registering and calling something that you can post without IP issues? Posting the source would help determine what might be going on.
  5. You absolutely can. However, and someone correct me if I am wrong, it is either one or the other. You can either export from Filemaker with xml/xsl to a Word document OR you can use the Word mailmerge function to create the document (with Filemaker data exported to xls, tab or csv.) For me the complexity, repetition and static nature of the export determine my approach. For instance, I have simple letter that is only sent out once a year that contains data from Filemaker. The static portion of the letter (that data which doesn't come from Filemaker) changes significantly each year and the data from Filemaker is not complex (a simple table.) In this instance I choose to export the data from FM to a tab delimited file and use Word to merge the data into the document. I also have several hundred individual forms that have to be updated by persons outside of my company. While this is only done yearly, the only change in the forms is the data merged from FM. So, in this case I use xml/xsl to export the forms to Word documents and group them in folders by the individuals who will be updating them. There are some quirks to exporting to WordML, for instance only about half of the people that update the above mentioned forms can actually open the WordML formatted documents. To fix this I wrote a script that would open each file after it was exported and SaveAs a docx. I am currently working on an example FM database that exports straight from FM to docx. I have the work that creates the document.xml file complete. I am moving on to the zip portion (docx files are actually zip files) and then will go back and work on the header.xml and footer.xml portions. Hope this answers more questions than is introduces. Jamie Forbes
  6. Yeah... The newer versions of ScriptMaster don't seem to be compatible with the SimpleFTP.jar. My recommendation is to spring for the 360Works FTP plugin.
  7. The solution is actually in the attached file on line 69. My problem was not with WordML code that I needed to generate. It was the XSLT code that is to generate the WordML. But, as I said, the solution is in the attached file. Thanks for the response. :)
  8. I don't know for sure that this will help, but it seems to me that you should be able to solve your problem with the 360 Works Scriptmaster plugin and some Groovy code. The link below is probably a good place to start for the Groovy code. http://groovy.codehaus.org/Validating+XML+with+a+W3C+XML+Schema
  9. OK... It figures that I would find a solution the same stinkin' day that I post the problem. Anyway, I have attached the modified stylesheet. See line 69, that is where all the magic happens. I will now begin creating the howto article. This article will be for me as much as anyone else. I find that I forget how to accomplish these complex tasks and the next time I need to do it I have to re-learn. CDxmltowordml.xsl.txt
  10. So, let me start from the beginning... I have had this ongoing project to get a report out of filemaker into Word format. Well, I have been able to slowly wrap my brain around this thing (atleast 90% of it, anyway). First, I created XML. This that is generated by a proof of concept DB. This code is created on the fly by calculation field and is fully qualified XML code (AFAIK). Next, I created the XSL Stylesheet that transforms the XML to WordML. The stylesheet does successfully transform the XML to WordML and it does it well, without errors. That is to say that it is error free on my system running the transform from the command line as well as from Filemaker using Scriptmaster. While it transforms the XML and takes advantage of BOLD, ITALIC AND UNDERLINE, it does not utilitize the color attribute that I have in the XML. Thus, my problem. The stylesheet does not transform the color attributes to the WordML. The code that handles the BOLD, ITALIC and UNDERLINE can be found in the loop that starts on line 66 of the XSL file. If it helps, the WordML for color would be . I have been unable to get the color value to go in the quotes. I am, of course, open to doing it another way if it needs to be done. I am kinda at a stand still here. Does anyone have any ideas about adding the code necessary to process the color to the stylesheet? I am hoping to get this thing wrapped up and start on an article to show how to generate WordML docs from filemaker. Thanks for your time, Jamie Forbes CDrecordset.xml.txt CDxmltowordml.xsl.txt
  11. I am soooooooo sorry for the delay. I have been somewhat busy. Anyway, I tried the method with the latest version of scriptmaster and I am getting a similar error. To that end, I recommend that you modify an email script that comes in the SM examples db or purchase the email plugin that 360 offers. If you need to keep copies in a local client, simply BCC the email to the appropriate account. Sorry that I am not more help than this. :
  12. Update: I just installed the latest java and no change. ScriptMaster no longer shows up in the list of available plugins. (Before or after the java update.)
  13. I am still supporting a few WinXP workstations that are running FMP 7v3. ScriptMaster 2.05a is not loading on them. : Is there a way I can download the last release that will load on FMP 7v3? Thx
  14. That is awesome! I appreciate the further feedback. Groovy seems to be a great scripting language. But, I have no experience with Java. So, I am experiencing growing pains. Your example is short, sweet and seems to perform better than the Class I picked up. I will be using it soon. And, of course, I will be implementing it in any future http post/get solutions as well. Thanks again!
  15. You need a an need an XSL stylesheet. The style sheet would be used to style the FM XML data as it exports. Maybe someone can point you in the direction of a tutorial. You can also check out the XML/XSL forum here.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.