Subtitles of the Movie

FileMaker 10 introduced new features that FileMaker Server 9 and FileMaker Pro 9 do not know about. So what happens when you use some of those features and host them through FileMaker Server 9 or host them on FileMaker Server 10 and then try to open that file with FileMaker Pro 9. We know that when the Server and Pro versions match, we will have no issues. But what about the other scenarios? In this movie we will discuss what happens when you mix and match FileMaker Pro and FileMaker Server versions. And for this we have FileMaker Pro 9 running on this Windows workstation and it has two copies of the same file open. One copy is hosted on FileMaker Server 9 and another copy is hosted on FileMaker Server 10. So if you get confused during this movie, just always check the blue fields here on the right. And we have the same files open running on an OS X workstation and opened in FileMaker 10. So this is a copy of the file hosted on FileMaker Server 9 and this is the copy hosted on FileMaker Server 10. So let's go down the list of some of those FileMaker 10 features that are totally new. Well, new to FileMaker 10 is this whole status area at the top of the window. You obviously will not see that when you open the file in FileMaker 9. FileMaker 9 still has the old status area here on the left. Now, if your solution depends on some of the new status area's functions, like the fact that you can have a saved finds, then that functionality won't work when you open the file in FileMaker 9. Script triggers are the other most of these new features in FileMaker 10, so how do they behave when hosted on FileMaker Server 9 or opened in FileMaker Pro 9? Obviously they will work when we just the file open in FileMaker 10 and hosted on FileMaker Server 10. If we go to Layout Mode here, we see by this little indicator that there is a script trigger attached to this field. So when we exit the field, this particular script will run. And we know it just works when we enter and exit, the script runs. Now, let's go to the same file opened in FileMaker 10 but hosted on Server 9. What happens if we enter the field and then exit it? As we can see, the script trigger still works. And that's because script triggers are a FileMaker client-only feature. FileMaker Server has nothing to do with it. So what happens if we go to FileMaker 9 and try the same thing? So this is the copy of the file hosted on FileMaker Server 10 and opened in FileMaker 9. If we enter the field, then exit it, nothing happens. And certainly nothing will happen if we use the same thing when the file is opened in FileMaker 9 and hosted on Server 9. If we exit the field, nothing will happen. And that's because like we just said, script triggers are a FileMaker Pro client-only feature. Now, some features however do depend on the FileMaker Server version. For instance, we know that FileMaker Server 9 and 10 both can do server-side scripts. The FileMaker Server 10 supports more script steps. And we know that FileMaker 10 has some new script steps. So if we make server-side scripts in 10 that use some of the new features and we then host the file on Server 9 and make a schedule to use that script, then that script will fail when it's hosted on FileMaker 9 because FileMaker Server 9 has no way of knowing what those new scripts are or plainly doesn't support some of the new script steps.