• Tour of interface, dependent on OS type

* Manage Database allows you to define Tables, Fields, and Relational Schema.  Support fields types are Text, Number, Date, Calculations, Containers, Time Stamps.

* Script Workspace allows your to write scripts or "code" in your FileMaker Custom Application.

* Layout Mode allows you to structure the UI.

* Difference between a brand new Blank file...versus a more completed FileMaker Solution.

* Compares Rows and Columns ... as they would be in a Excel file.  

* The database Structure and data are saved in the SAME file.  File may get large....due to data growth.

* A FileMaker Solution... may be a single File... or multiple files.   A solution with multiple files... should stay together in a single directory.

• Status Tool Bar is a standard part of the FileMaker Application.  The developer who built the solution May or MAY NOT choose to display the Status Toolbar.

 * Quick crash course of how to use FM Pro

 * Launch Center allows you to browse through the local files, or open files on a server/host.

 * A server connection can be set up from Hosts tab. Click on the "+" symbol on the lower corner of hte window. Enter the correct IP address and label it with a easy to remember nickname.

 * The top status bar allows for navigation/interaction with records. Creation or deletion of records. This tool bar can be risky if you don't what you are clicking on. Displays the current found set of records.

 * Layouts is just a GUI (Graphic User Interface) that is based on a specific table. It's a way of displaying information from a table/record on screen. 

 * Layouts and tables are created by the FM developer.

 * Saving data in FileMaker is easy. Making an edit will automatically save once you leave the field you are editing. Be careful, there is no undo function. Edits are permanent.

 * Multiple users cannot edit the same record at the same time. But they can view the same record at the same time. 

 * Something to be aware of when employees leave the workstation. Danger of record locking a key record.

 * Multiple database files can communicate with each other. But there must be as many windows open as there are different files.

 * Having multiple windows/files open at the same time can be confusing for the user. Up to the Developer that the interface and navigation make sense.

 * Layouts are based on tables and displays the data from records in that table. 

 * Tables can be related to each other. Data links can be constructed which allows for record data to be seen from other tables/layouts. This is the main feature of a relational database. 

 * Changing data from one table, in a record that belongs to another table, causes the data to permanently change. 

 * Editing a record = Record Locked

 * Commit a record = Record Unlocked and Saved, no undo for this process

 * Deleting Records is Permanent.

 * There is no undo for record deletion. Deletion is a permanent action Furthermore there is no log of the delete action.

 * Generally speaking, deletion should be a last resort, instead consider marking a record as "dead" or "inactive".

 * Records can be locked in a Multi-user setting.

 * When a user clicks in to a field to edit it, on a layout, that record is called locked. This means that no one else can edit fields on that record.

 * Each database that is opened will have at least 1 window open at any given time. Close all windows on an open database file will close the file.

 * Having multiple windows open on a single database file means you can look at 2 records at the same time. Or you can maintain 2 found sets.

 * FileMaker treats having multiple windows open on 1 database file kinda like a second user.

 * IT may need to coordinate with a FM developer.

 * Having an in-house developer is nice, since they are always accessible, and more likely to understand your business process. They save time, requires less data entry, and generally commit fewer mistakes.

 * The IT staff should not feel threatened by the developer. They are there to help. IT staff should come to the developer with questions, and learn it's behavior. Understand the requirements to support the files the developer is creating.

 * Once a user has a finished solution, and it is thrown on to a server, it can still be developed and edited. This is the advantage of FileMaker.

 * Custom Application is also known as a database or template. 

 * FileMaker is a database engine, custom application, and scripting environment. 

 * FMS can mean the hardware or software. 

 * FM Go can connect to hosted files on FM Cloud or FMS.

 * FM Go does not include development and is used for remote access. 

 * FM Direct allows users to remote access onto html.

 * 5% or less packet loss is usually okay. 10% loss is bad. 

 * Users in a multistory building accessing the server on different floors will connect in 1-2 milliseconds. This means FMS is fast!

 * It's important to measure latency and keep servers as close to possible, so your application doesn't lose performance.

 * Asking questions is not a sign of weakness. 

 * Ask questions related to security policies to ensure your add correct safety features. 

 * Ask the FileMaker Developer a question for specific information to complete a project accurately. 

 * Can reach Richard Carlton Consulting at support@rcconsulting.com

 * FileMaker Cloud is FileMaker Server on Amazon Web Services.

 * FMS can still be installed on an Amazon Server.

 * FMS can be on Vultr or Rackspace. 

 * Server side plugins are highly recommended. 

 * Make server plugins are available on your platform. 

 * FileMaker has a QA process for FileMaker Cloud servers. 

  * FIleMaker Cloud is tuned for Linux and Amazon Web Services. Does not work with Microsoft Azure. 

 * FileMaker server supports the latest and last version of Oracle and SQL.

 * FileMaker Cloud is moving towards running on REST API engine. 

 * FileMaker Server you need to PHP, XML, and/or ODBC. 

 * If you have data center centers, turn on point-to-point and encryption at rest to protect your data. 

 * One FileMaker plugin is the PayPal plugin to process a credit card. 

 * There a plugins for QuickBooks and for Word. 

 * Make sure you have proper licenses purchased and make sure it works for your version of File Maker. 

 * Windows for a server require a 64-bit plugin. 

 * Some plugins may have to be recompiled for LInux if you are using Linux.

 * Have a layout devoted to reporting bugs. 

 * Have users attach screen shot of bug, location where bug occurred, and result of the bug.

 * If bugs are reproducible on multiple machines, definitely report it to FileMaker Inc. 

* Log into FileMaker website to report an error. 

 * It's important to include what the behavior should be in the bug report and what actually happened.

 * FileMaker Knowledge Base is found on the website and it contains a list of all software patches and various other common topics related to FileMaker.

 * An issue that can happen in FileMaker is the web viewer will crash. Restarting FileMaker can fix this and also restarting the computer can fix it. Restarting can fix many issues. 

 * Companies with fifty or more employers can integrate Active Directory in FileMaker. For the smaller, companies FileMaker has its own security features.

 * Passwords can be hard-coded into the FileMaker System or managed by scripts or can be integrated with Active Directory through FileMaker Cloud. 

 * Most developers will have admin credentials that can access layout modes and then have user credentials to read and write. The user credentials are usually shared and this is a bad idea

 * Can add timer script step to automatically lock.

 * Can also manually lock screen.

 * When you build a server you give it a static IP or a domain. 

 * An important part of setting up a FileMaker server is the creation of an approved SSL certificate. 

 * Local host port is 16000 and remote connection port is 16001.

 * Under statistics, you can tell what clients are currently on the server. 

 * Also in statistics, you can FMS collect various data and create charts.

 * The tab to the left is split up with operation and settings for FMS.

 * FM Cloud does not have XML or PHP engine. It also doesn't have statistics or logging.

 * Status will show errors

 * Displays IP address

 * Shows server version rather it's 16.0.1, 16.0.2, 0r 16.0.3. After three is usually a new release.

 * In the activity tab, you can open folders and get backups. 

 * Anytime you do anything even in activity, the log will report you opened the file. 

 * Log file can tell you if you didn't close the file properly. 

 * Cloud backup usually occur every 15 to 20 minutes. 

 * Best backups prepare for stolen servers and drive failures. 

 * Schedule tabs tell you when your last backups occurred. Usually should have several backups. 

 * Database server setup restart crashed files.

 * After two minutes of inactivity are disconnected. 

 * FMS is backwards compatible for clients in 16 who can access 15.

 * FM Cloud you must be on the same version or newer. 

You need to setup your backups... or you will pay!

* 3 Types of Backups... Bootable, Scheduled, and Offsite.  You need them all.

* (MAC Users) Sync2Folders... is the old shareware version.  They now have a updated professional app... called "Sync Folders Pro" on the Apple App Store for $7.99... which works pretty well.   This App will not Zip the files during Sync.

* (MAC Users) "Get Back 2" is a similar App... but compresses the backup during the transfer.   Very clever.  

* How many backups should you have. Onsite or off?

* What is a cloned drive and what value does it offer?

AKA Incremental Backups... Super fast!!!

* These backups are highly automated and result in FileMaker only saving "changes" to databases during a backup... and not entire copies of a database.   So if a 4 gig database has 20K of new data... progressive backups will only write 20K of data instead of the whole 4 gigs... so its super fast!!!

* NOT * A Crash from FileMaker Cloud

* Always restore from the last good backup.  DO NOT use crashed databases.

* If you're using FileMaker Cloud, you're procedure is different

* There is a specific procedure for restoring from a crash on FileMaker Server.  

* You may want to create your own variation of this procedure for your organization... but keep your eye on the fundamentals.  

* Discussion includes conversation about "HardLinks"

* FMS has a default preference of ALWAYS trying to open the local files automatically... whenever it boots up.  TURN this OFF.

* When the database Server crashes, take the crashed files out, date them, and compress them.  Do NOT delete them.

* After the Restart of the server... Find the last good backup, and make a COPY into the Data/Database folder.

* Crashes CAN occur in the middle of a backup.  DO NOT use these.

* Restoring the files on a Mac... requires reset the correct Permissions to the FileMaker Files... BEFORE you start them up on the FileMaker Server.

* If you fire up files... and you find that you cannot EDIT the data and the Files are set to "Read-Only"... the permissions are WRONG.

* To fix FMP12 files that have the wrong permissions....CLOSE the files FIRST... then Fix them... then Reopen then in FileMaker Server.