Now that fmSpark is functionally complete, it's missing something. Specifically, it's missing sample data. We can't simply dump in a list made-up names and addresses and create random data; fmSpark needs data that looks good, by which I mean templates that demonstrate how good your email (and letters and labels) can look using fmSpark.

As we get closer to pushing fmSpark out the door there are a few issues remaining to be finished off. Having been in this business for more years than I care to admit, I am nevertheless surprised when beta testers find bugs that were missed during development. No matter how much time you spend with the product, refining and tweaking and bug stomping, there will nonetheless be a few that slip out the door. I'm happy to say that all known bugs have now been squashed and fmSpark will be released shortly.

We have had several ProofSupport inquiries recently that have begun with, "I'm not sure if you can help us. We're still using FileMaker Pro 6, and we are having trouble with..." Now, there is no question that we spend most of our time with FMP 9, but we are still very comfortable with FMP 6. 

A fairly common question when preparing to integrate your web application’s MySQL database into a FileMaker solution using ESS (External SQL Sources) is, “What information do I need from my hosting provider to connect to MySQL?”

The list is pretty straightforward, and you’ll probably have an easier time asking your hosting company for these MySQL specifics than trying to explain FileMaker ESS:

Thanks to everyone who stopped by the FileMaker booth at FETC and took some time to chat with us. I was particularly pleased to see the interest in ProofSupport. We heard both from visitors to the booth and from the FileMaker folks that there is a need for top level support and advice that goes beyond the technical support that FileMaker is able to offer themselves.