FileMaker Sync with MirrorSync

/

Synchronisation is important for remote users who do not have constant connectivity.

There are several FileMaker 'Add-ons' that provide automatic sync of filemaker records. One such solution is MirrorSync.

In this YouTube video Jesse Barnum, of 360 Works, and Richard Carlton discuss and demo the new MirrorSync 2 FileMaker extension.

Starting with a single user is free. For more users there are incremental licensing costs.

 

Create a Mobile App — Webinar

/

Recent Webinar Promo from FileMaker Inc:

Get started with mobile app development.

If you are looking at creating a mobile app, where do you start? This webinar will lead you through the steps for planning, creating and deploying a mobile app for your business. We will use an example business use case to illustrate the process and what is possible with the FileMaker platform. From identifying the pain points through to the vision of what success looks like, we will show you the steps to building a mobile app and give you the confidence to get going right away. You will see demonstrations building a proof of concept and prototyping. Finally, you will discover a range of resources to get you started on your journey.

Tuesday, 29 September 2015
75 minutes
2.00pm - 3.15pm AEST

 

Some Version Info

/

While version have changed over time all the way up to the current v14, the FileMaker file format has also changed a couple of times.

From fp4, fp5, a major change to multi-table with relationship graph in fp7 and most recently to fmp12 (the current format). Format fp5 will work with v5, 5.5 and 6. Format fp7 will work with v7, 8, 8.5, 9, 10 and 11. Format fmp12 will work with v12, 13 and 14.

FileMaker Conversion (Upgrading in a Nutshell)

/

To convert (multiple) fp5 files to the latest version follow these steps*

1. Run DDR in v5.5 or 6
2. Make sure all file have same full access password
3. Run MetadataMagic on solution if possible
4. Purge unused elements
5. Make sure unique names for relationships/layouts/valuelists/scripts before conversion
6. Name relationships like this: client_INVOICE_st_cre_det
7.  Record all layouts visible to user
8. Record scripts visible to user
9. Some scripts will need a Goto Layout added to the start to work properly in consolidated solution
10. Manage moving to layouts and back to original when running External scripts
11. Consolidate Value Lists
12. Change field names to standard
13. Use FMv11 to convert files from fp5 to fp7
14. Convert to fmp12 using FM12/13/14
15. Copy and paste TABLES into single main file (review import.log created after this)
16. Add relationships
17. Fix field errors (auto-enter/calculations/lookups)
18. Add layouts with exactly the same names as used in original individual files and set form or list / print margins
19. Add value lists (consolidate where possible)
20. Import scripts from files (errors in import.log)
21. Copy and paste layout elements into new layouts
22. Set tab orders
23. Change any external script references to internal (consolidate)
24. Set up custom menus if required
25. Also check the following:

  • Review Go to Related Record calls to ensure you are in the correct context/layout. Once consolidated the Go to Related Record may incorrectly state ‘current layout’ to the related table.

  • Review all New Record, Duplicate Record, and Set Field calls to ensure a commit record request is present to prevent record locking.

  • Check Import Records script steps

  • Export Records where a Group By is checked

  • Custom Functions, if going from FileMaker 8 or higher

  • Adjust Window Hide, remove them from the files that have been consolidated or the main window will hide

  • Close File, remove them from the scripts or the main file will close.

  • Any field validation may need to be reviewed as in .fp7 field validation occurs when any field is modified and the field may not be present on the layout.

* Based on a USA-based dbservices article.

  

/ /

Peter Harris

Inspector Pro 5

/

Inspector Pro is a powerful tool for analysing your FileMaker database. It provides a 'database of the database' by drilling into the structure of the system. You need the advanced version of FileMaker Pro to produce a Database Design Report (DDR) that is processed by Inspector.

A useful demo video is here

/ /

Peter Harris

Software Requirements Template

/

If you want to prepare a comprehensive description of what your system should do then a template like this might be handy.

Another option is for Cognitive to write a specification with you.

For small systems we can work from a high level outline of the requirements.