I know I've been quiet of late. But I've been working.

You see a few weeks ago I had this checklist up on the site:

• Make sure apptacular_blog database works on MySQL on MAC.
• Make sure apptacular_blog database works on MySQL on PC.
• Make sure sakila database works on MySQL on MAC.
• Make sure sakila database works on MySQL on PC.
• Make sure apptacular_blog database works on MSSQL on MAC.
• Make sure apptacular_blog database works on MSSQL on PC.
• Make sure adventureworks database works on MSSQL on MAC.
• Make sure adventureworks database works on MSSQL on PC.
• Fix major issues in code readability.
• Start Document how to work with Apptacular

See those AdventureWorks database items? They nearly killed me and made me want to stop work on Apptacular. AdventureWorks is like a cruel Double Dare obstacle course for code generation:

• Composite primary keys
• Composite foreign keys
• Composite primary keys that are also foreign keys
• Custom Datatypes
• Constraints (Really only affected unit testing).

I came through, and now I can give you this list:

• Make sure apptacular_blog database works on MySQL on MAC.
• Make sure apptacular_blog database works on MySQL on PC.
• Make sure sakila database works on MySQL on MAC.
• Make sure sakila database works on MySQL on PC.
• Make sure apptacular_blog database works on MSSQL on MAC.
• Make sure apptacular_blog database works on MSSQL on PC.
• Make sure adventureworks database works on MSSQL on MAC.
• Make sure adventureworks database works on MSSQL on PC.
• Fix major issues in code readability.
• Start Document how to work with Apptacular

So that's where I am. A few of you asked if you could get your hands on Apptacular and I would be happy to distribute it to individuals. I'm not ready for general availability yet though.

And as a final note, I thought I would share this feature with you: Apptacular can model CRUD for image fields in your database.

Apptacular ColdFusion Builder Extension - Working with Images from Terry Ryan on Vimeo.