For the first database, there was one container field in one table with 68K records. It then compressed the database to reclaim the unused space. FileMaker Pro started moving the documents in the container fields to a folder called “Files” outside the database. (You could also use BaseElements or Inspector to search by field type.) For each container field, I changed the storage option to “Store container data externally” under Field Options.įinally, I closed the Manage Database window to save the changes. Next, I went through each table looking for the any container fields. Next, I opened the database and sorted the field list by “field type”. Fortunately, FileMaker 12 has a new feature called Enhanced (or external) Container Fields to address this.įor each database, I converted it by dragging the file onto the icon for FileMaker 12 and going through the automatic conversion process. The disadvantages of a large database in FileMaker are several including slower performance (more data to push over network), lower productivity (long wait times during backups), and greater risk (more susceptible to corruption in the event of a crash). The result in each case was database bloat-a file size much larger than necessary (1GB or greater). Both customers were embedding documents in the database by inserting them into container fields. But once it's working, it works - at least that's my experience.Recently, I converted two customer databases from FileMaker 11 to FileMaker 12. The only solution I know of is restarting things. Getting the "host's capacity" message is something that has happened to me when installing plugins some times. You'll then want to restart the database server and possibly the script engine. Now scan the listings to make sure everything is fmserver:fmsadminįor any you find which are not set with the fmserver owner and fmsadmin group then you'll needed to change them with chmod (run 'man chmod' for more info) Within the Terminal you would check this by using the following commands (this is for Mac - Windows would be different)Ĭd /Library/FileMaker\ Server/Database\ Server/Extensions You may not be able to update it if it isn't owned by the fmserver:fmsadmin user and group. You mention the plugin was "installed manually" and if it was copied then you need to check the permissions and ownership on it. FileMaker Server is probably very permissions sensitive - as is the case with most daemons. I have come across similar issues and I don't know what the reproducible steps are. This video provides all the critical know-how in order to start working with PSoS and it will get you going fast! You can update hundreds of thousands of records with lightning speed or generate a hundred page report as a PDF within minutes instead of hours. You can send hundreds of thousands of emails without ever seeing a spinning waiting indicator. With PSoS, you can import hundreds of thousands of records in mere seconds. If your solutions are stuck in versions prior to 13, then you might want to beg, borrow or steal (ok, not steal) to start using this feature. Changing the way you think about FileMaker development, using PSoS for short, is inevitable. Until you start using it, it "seems" like it's just "another feature". This is essentially what this new script step does, but with all the power of what FileMaker can do. Your client, a web browser, makes a request to some beefy server and it wrangles the data and then reports back with the compiled results. This is fundamentally why the web is so popular. There's so much power in how it can be used, that it truly is a game changer. Yes, I said that with all caps! This is exciting! Perform Script on Server is the one step which will change how you develop FileMaker solutions FOREVER.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |