- #Filemaker pro 6 tutorials mac os#
- #Filemaker pro 6 tutorials install#
- #Filemaker pro 6 tutorials update#
- #Filemaker pro 6 tutorials pro#
#Filemaker pro 6 tutorials update#
Click the Files tab and check the box for the Auto Update preference. Select FileMaker Server in the console tree and choose Properties from the Action menu. On Windows, open the FileMaker Server Console.
#Filemaker pro 6 tutorials mac os#
Setting the Auto Update preference on Mac OS 8/9. If the FileMaker Server is running on Mac OS X, launch FileMaker Server Config and select Preferences from the FMServer Config menu to find the Files tab and check the box as in Mac OS 8/9.
#Filemaker pro 6 tutorials pro#
Click the Files tab and check the preference for “Allow FileMaker Pro guests to download updates automatically” (Figure below). For Macintosh systems running Mac OS 8 or 9, select Preferences from the Edit menu. This is done slightly differently depending on the platform that FileMaker Server is running on. The AutoUpdate function takes care of installing the plug-in to the correct location and enabling it so that FileMaker doesn’t have to be relaunched.įor the Auto Update plug-in to work correctly, FileMaker Server has to be configured to allow client machines to update plug-ins. If the version of the plug-in on the server is later than the version on the local machine, you use the FMSAUC-UpdatePlugin function to download the newer version of the plug-in to the local machine, replacing the old version and enabling the new version. You’ll use the Status(CurrentPlatform) function, you check which platform you are running on, and depending on the results of this function, you check for the specific plug-in version for that platform. (This must be done on a platform-specific basis.)
The procedure for updating a plug-in is to check the version of the plug-in installed on the client computer (by using the plug-in’s own external Version function) against the text file that stores the version number of the plug-in on the server by using the FMSAUC-FindPlugin function at the start up of your FileMaker system. In addition to the plug-ins, this folder also holds text files that store the version numbers of the plug-ins.
The plug-in works by keeping versions of the plug-ins you might want to update on the server in a folder called AutoUpdate. The Auto Update plug-in renders this obsolete, allowing you to place the plug-in on the same machine serving the databases and have users receive the new version of the plug-in automatically the next time they log on to the system.
#Filemaker pro 6 tutorials install#
If you’re using a plug-in on a network of dozens (or hundreds) of users, and a new version of the plug-in is released, you used to have to physically go to each computer system and install the plug-in. One of the challenges with working with plug-ins is keeping them up to date.
After a brief introduction to each plug-in there are some real-world examples of how the plug-in might be implemented in a database system.įileMaker 5.5 introduced a new feature with the release of the Server version. There are generally discounts for multiple copies and different pricing for developers. This usually isn’t the only kind of license available for plug-ins. For each showcased plugin, you’ll also get information about where you can purchase it and how much a single-user license costs (at press time anyway). Once you’ve learned about the Auto Update plug-in, we’ll review a number of other third-party plug-ins that you may find useful. (FileMaker includes other plug-ins, such as the Web Companion, Local Data Access Companion, and Remote Data Access Companion. (Be sure to check out the Web sites of the publishers of each plug-in for the most recent versions.)įirst you’ll learn about the Auto Update plug-in that is included with every copy of FileMaker. So instead, we’ll discuss some of the most useful plug-ins and see examples of how they work. Covering every plug-in available, in addition to being obsolete by the time you read this, would probably make this book twice its current size.
0 kommentar(er)
