Subtitles of the Movie

As you can see there's quite a few new FileMaker Pro 10 features. We're going to try and cover each one briefly and some in greater depth. For instance, when we look at Bento integration, it's very simple, there's not much to it, you can either create a new FileMaker database based on the Bento source or import records from Bento source. It's that simple, we'll just cover it briefly. But in the case of script triggers which is on the other extreme, we're going to have an entire chapter devoted to script triggers in the Advanced tutorial. So, if you thought that was all the new features, well you're wrong. There an additional set of new features here. So there's 2 slides of new features here, it's a major upgrade. You'll see for instance, Seffield by name, one of my favorite new features and also SMTP, Send Mail Script Step. So great features will cover these 2 more in-depth as we go along. Let's get into covering everything that we've seen these slides so you can get a good idea what the new features are. So we'll start with Bento Integration, you can either import from your Bento 2, not Bento 1, only Bento 2. You can import to existing FileMaker Database or you can actually create a new FileMaker database from your Bento 2 data. If you import you're going to get the Field Mapping Dialog you're used to when you do an import so it'll be very familiar. And to create a new database from a Bento source you just go to the Quick Start Screen, which we're going to do right now. So do New Database, you'll see this new radio button here, this is new for FileMaker 10 and you can actually create a new database from quite a few sources. One happens to be Bento. When you choose it and click OK, it's going to ask you to choose what from your Bento to data source you want to import or create a new database from. Notice I didn't have to locate it, it found it for me on its own. So we'll choose address book here, an entire library, click Continue, we'll save it on the Desktop and there it is. Two records in my address book, you'll see there's one for me and as we scroll over here, the other ones for a company called Apple Computer. There's not much filled in here but you get the idea. It's very easy to do, makes a really raw database for you and it's up to you at that point to go ahead and put the interface on it. But it's a great way if you're moving from Bento 2 to FileMaker; it makes it very easy to do that. Now you could also go ahead and choose Import. You'll see the Bento data source is right there. Works just like your regular import. Once you have chosen the data source it'll put up the Field Mapping Dialog and it'll be very familiar and very easy if you've ever done any kind of importing. We'll move on here, let's talk about some of the new functions. There's one called the Char Function. Now this one isn't going to make much sense on how to use it until we get into script triggers. But as you can see it returns a value representing 1 or more Unicode Points. So we supply at the Unicode Points right here, it returns the value, in this case an A. Or we could supply more than one Unicode Point and they'll return more than one value, in this case A and B. And remember the values in reverse order; notice that 97's here but it's here. That means that you would have thought maybe that would have come last but it actually comes first cause it evaluates in reverse order. And again it won't make a ton of sense until we start working with trigger modifier keys and the code function, which we'll cover next. So hold on, you may not understand it yet but we'll get to it. And then the code function is essentially the opposite of the Char. You supply it with a value and it returns a Unicode Points. And again, you'll use it with Get Trigger Modifier Keys, Get Trigger Key Stroke and Char Function, essential script triggers. Then we also have the Get Field Name Function. Now this one's really handy when you think about the new feature set field by name. This is a new script step, so you usual combine these 2, I'm not saying it's the only way to use it but this is going to be a common way to combine these 2 to make very dynamic scripts. So essentially what it does, you supply it 1 parameter and it returns a table and field name. So for instance if you said get field name, self inside of a calculation, it would return the table and the field. A more likely scenario will be inside of a script where you'd say get the active field name, that would be where your cursor is blinking, whatever field it's in right then. You'd then surround that with the evaluate function and then get field name and it would return the fully evaluated name of your table and field so that you could use that inside of a set field to go ahead and dynamically set that field. So you can see how it might be handy, it might not be totally clear right now because it really requires a complicated example and we'll see that as we go through the rest of the tutorial.