Subtitles of the Movie

The second example is a VBscript. What this VBscript will do is it'll retrieve some data from our sales numbers database, hosted on this particular FileMaker Server, and it'll create a PowerPoint presentation, just one slide, but with a graph of our chosen data. Again, the logic here is the same thing. By using our inputs when we run this VBscript, we are going to construct that URL under the hood and then work with the XML document that FileMaker gives us back. So let's go ahead and execute this. So what year do we want? 2006 is good. What region do we want? Colorado is good. This is the exact URL that the VBscript will execute for us, and there it goes. So the bottom line is this: the XML publishing engine that we find in FileMaker Server is truly powerful. It's a true gateway to allow FileMaker data to be used in just about anything out there. You'll find it under Web publishing, but that's a bit of a misnomer because using that FileMaker data is not limited to just being used in a website. It can be used anywhere that XML data can be consumed. It could be a Desktop application, could be a Web service, could be a website, could be a Smartphone. Anything out there that can consume XML is a prime target for our FileMaker data and we know that FileMaker, Inc has its own PHP API. We've already discussed the fmDotNet API and there are other alternatives out there, like the FlexFM API, hosted by Soliant, and it allows Flex developers to use FileMaker data and, again, the premise here is that those developers do not need to learn anything about FileMaker. They don't need to learn about that URL. They don't need to learn about FileMaker's XML grammar. They can use their own code and interact with FileMaker data. Another example out there is the Ruby for Rails API for FileMaker. Same thing. It lets Ruby developers use FileMaker data without having to learn anything about FileMaker and that is the true power of the XML publishing engine.