Subtitles of the Movie

Now that we have FileMaker Server installed, let's have a look at what is required to actually host files. Before we start, and it may be obvious, but FileMaker 10 can host files created with FileMaker 7, 8, 9 and 10. Basically all of the files that share the same file format and the .fp7 extension. If you have an existing FileMaker 5 or 6 solution with the .fp5 extension, then you will need to convert those files before they can be hosted on the new FileMaker Server. We have the file here locally on the machine that has four accounts, the usual admin accounts and three user accounts and two custom privilege sets; group A and group B. The file is also not set to log in automatically here in the file options. This setting is off. Usually it's on by default and it uses the admin account, but we've toggled it off. So whenever you try and open the file, you will always be prompted for an accounts. This file is not hosted yet. We have it open locally on our workstation and as you can see, we can login to the file with any of those three accounts. We can use User 1 and you can see that it properly reflects who we are. We can use User 3 and there we go. So let's go ahead and use the Server Admin Console feature that let's us upload the file to FileMaker Server. So let's quit out of this file, navigate to our FileMaker Server Admin Console and this is the Admin Console running locally on our OS X workstation but the server, FileMaker Server 10 is installed on Windows 2003 at this IP Address. And as we can see, we currently have no files hosted. This is the usual FileMaker Server sample file that comes with the FileMaker Server installation. What we want to do is upload a file from a workstation to the remote server. So in this first dialog we'll just go ahead and pick a database. It's on our Desktop. There's the file. Now, it's easy to skip by this page but there's a very important note here. It says that if none of the privilege sets allow for access to the network, then that privilege will be added to the full-access privilege set. So what does that mean? Well, let's back out and go back to our file. If you look at the privilege sets that are in the file, then we note that none of them have this particular privilege set enabled. What this means is that if we move the file to FileMaker Server, you couldn't access it. This setting here controls where the FileMaker Server will host the file and will let users connect to it from a FileMaker Pro client. As we can see, none of them have this particular setting. So what happens if you forget? Well, that's what the message on the Admin Console is all about. FileMaker Server will automatically enable this particular privilege for the full-access accounts if you forget to enable that FM App Bit in any of the privilege sets. If that privilege, the FM App Privilege Bit is set in any privilege set, any one, then FileMaker Server will not touch the file. It will just move the file and whoever has an account that belongs to the privilege set that you've enabled the FM App Bit for will be able to access the file. So we'll leave the file as is. None of the privilege sets have the FM App Bit set. It will go ahead and upload that file. We'll pick it up from the Desktop and let it upload. So the upload is done and the Admin Console properly reports that the file was successfully uploaded and has been opened. And as we can see it here. Now, if we go back to our FileMaker Pro and open the file remotely, you see that we can get in with the admin account, which is the full-access. So if we now go and have a look at those accounts and privileges, you'll note that FileMaker Server has only enabled this bit for the full-access accounts. None of the other privilege sets will have it. So if we now try and login to the same file with one of the user accounts, we won't be able to get in and we won't be able to get in until we go into the privilege sets and for those users manually toggle on the access to FileMaker network, the FM App Bit. If we now try to login, you'll see that we will get access to our file from the remote workstation. There we go. So using the Admin Console Upload Feature is the preferred way of moving files to your FileMaker Server, but it's certainly not the only way.