How many times do users let you know of a bug in their solution and yet are unable to provide any detail about what they were doing at the time? What layout were they on? What was the found count? Were any plugins installed? What record were they on?

These are very common questions the developer may ask and yet not receive a good answer to. To remedy this we have built a nifty debugging script that can provide the developer with these answers. In this article we'll go over in detail what is captured in the debugging report and ways you can best integrate it into your solutions.

In this article we talk about circular references and how these can occur between two auto-enter calculation fields. We talk about what happens in this situation and what we might expect a desirable outcome to be. We then provide a solution to this problem by showing how circular referencing can be overcome using control flag variables to dictate the order of execution of these auto enter calculations.

In this article we look at a simple way to implement an instant messaging chat display in FileMaker using basic HTML and CSS (No Javascript required!) 

A cool javascript based color picker widget for Claris FileMaker Pro and WebDirect solutions

A technique to commit records held up by pesky users who leave a record locked for too long...

Here we present a simple and reusable FileMaker script that is capable of performing any existing script server-side using the Perform Script on Server step.  A single line of code at the top of any script is enough to run that script server-side.

Here's a nifty utility to help developers quickly and easily derive modifier key numbers as well as codes for various keystrokes pressed...

This is a really simple and reusable script for obtaining any entire record as JSON without knowing it's field structure...