Our client, is in the textile business and manages their manufacturing processes using multiple FileMaker application files. We helped them migrate from the FileMaker 5 version to the then latest FileMaker version. Their biggest pain point was, they had thousands of Formula files as separate FileMaker files. Each Formula file contained a formula/recipe for a program used by this 24×7 operation.

The shop floor used a base template that was modified for each specific program. Each program had different processes. The layout design, as well as the placement of processes and some values on the layout, varied from program to program. Some formulas required added steps like preheating before adding specific dye material, whereas some formulas need it after adding the material. Due to these differences, they maintained separate Formulas or Program files.

This blog describes how we provided them with a solution by addressing their pain points.

The Old Process:

• For every new formula, the user had to create a copy of the FileMaker file, rename it and make modifications to suit the new program.
• The user had to manually enter the Program Number.

The Pain Points:

• A huge number of files as a new file had to be created for each new Program.
• Time was spent in creating new formula files.
• Files could not be hosted on one FileMaker server since there were more than a thousand files generated.
• Manual backups were needed.
• Risk of file corruption.
• Additional memory needed to store and back up files.
• Upgrades were time consuming and difficult in a 24×7 operations.

The Solution:

• We provided them with a solution which reduced the number of files required.
• Instead of creating new FileMaker files for each new Program, we suggested they create a new layout in the same FileMaker file.
• Each layout name was to follow a naming pattern starting with the Program number. Ex. for Program number 111, the layout name would be 111.
• The naming convention could also include specific attributes of the Program which helped in easy identification.
• Program numbers were auto-generated, and manual entry and duplication avoided.

So, instead of creating new FileMaker files each time, few common FileMaker files were created for different fabric types (ex. Cotton, Polyester) and then hosted on the FileMaker server. These files would then be used to create new layouts. The common files were further customized as needed and they were matched to the behavior of separate files—for example, functionality to find a specific program and to generate a found set that belonged to it.

We found the batch number as defined in the Program. Every time a new layout was created for a program, the system would generate a default record for that Program.

Result:

• Formula files were reduced to 4-5 from thousands.
• Files were hosted on the server and were more secure.
• No manual backup needed.
• No risk of damage or corruption of the files.
• Time was saved since no new files needed to be generated for every program.
• Auto-generated program numbers made it more user friendly.
• Since then the client has been able to upgrade to the later FileMaker versions very smoothly.

MetaSys has a large team of experienced and certified FileMaker developers,with experience in FileMaker 5 to the latest FileMaker versions. For any queries, please feel free to contact us.

Security plays a vital role in any software application. Most of the time, standard approaches, like Startup login, encryption of password, etc., are followed. ‘Manage Security’ section of FileMaker provides different types of settings to manage various levels of access as well as privileges to the logged-in user.

Encryption at Rest goes beyond this by providing security to the FileMaker file when it is physically stored on a disk. Encrypting a database provides additional security to your FileMaker application.

What you need?

To encrypt one or more database files in FileMaker, you will need:

• FileMaker account with [Full Access] privilege
• Encryption Password
• A shared ID

Steps to follow:

To encrypt a database, you should have the required FileMaker files stored locally. If the files are hosted on the server, you will need to unhost them, perform EAR, and then host again.

• In FileMaker Pro client, go to menu ‘Tools >> Developer utilities’.
• Add the files you need to perform encryption on. In the case of a multi-file solution, add all the required files.
• Specify one of the files as Primary.
• Select the Project folder, where you would like to place the encrypted files after EAR is completed.
• Under Specify Solutions options, select the ‘Enable Database Encryption’ option.
• This will automatically select the option above ‘Create Error log for any processing errors’. This log is important (but optional) since it creates a log file in the EAR folder. This file will let us know if the encryption was successful or if there were any errors. In the case of multiple files, the encryption status of each file is logged.
• Specify a Shared ID; it links multiple encrypted files.
• Specify a FileMaker Account with [Full Access] privilege. This will be for the Primary file specified above. If the other files have different [Full Access] password, then it will be prompted during the EAR process.
• For the files, which are linked with each other via ‘External data Source’ and have different [Full Access] credentials, the login may be prompted more than one time for the same file.
• Specify the encryption password. In case of multiple files, if the files’ encryption passwords and shared IDs match, the user will not be prompted again for the encryption password. Enter a password hint, if needed.
• The option ‘Keep ‘Open Storage’ is checked if you do not want the container field data to be encrypted.
• Click ‘OK’ to start the encryption

After EAR completion:

• After the EAR process is completed, check the log file for encryption status.
• In the case of external storage container, the EAR process will create the same folder structure for each file. Container data will be encrypted/not encrypted depending on the EAR option specified above.
• Users will be prompted for encryption password when opening the files via FileMaker Pro or FileMaker Go locally.

• When the files are hosted on the FileMaker Server or FileMaker Cloud, users will be prompted for the encryption password before hosting. This password can be saved to automatically open encrypted files when the server restarts.

Remove Database encryption:

You can remove database encryption applied to a file or a set of files. It is a similar process as that of encryption.

Under ‘Tools >> Developer Utilities’, add the files you want to remove encryption from, select ‘Remove Database Encryption’ option. You will need the Encryption password and [Full Access] login details of the FileMaker files.

Encryption at Rest is an essential aspect of data security in FileMaker. By following the above steps, you can encrypt your FileMaker database to provide an additional layer of security. If you have any doubts or need assistance, reach out to the team of experienced and certified FileMaker experts at MetaSys Software, your custom software development company.