Our Blog, Filemaker only, Xojo only, Archive (older), Follow us on Twitter, Xing, LinkedIn or Facebook.

MBS FileMaker Plugin Schulung auf Deutsch bei der FMK 2017

Friday 20 January 2017 at 1:33 pm
Auch 2017 biete ich wieder eine MBS FileMaker Schulung auf Deutsch an.
Am Tag vor der FileMaker Konferenz in Salzburg, am 11. Oktober 2017 (Mittwoch) von ca. 9 bis 17 Uhr.
  • Neues im MBS Plugin.
  • Rundgang durch Beispiele
  • MBS Plugin verwenden mit FileMaker Cloud
  • MBS Plugin verwenden mit FileMaker iOS SDK
  • Erweiterungen im Skript Workspace
  • Beliebte Pluginfunktionen
    • FTP/SFTP Up/Download
    • Webservices einbinden
    • Bildbearbeitung
    • Barcodes generieren und erkennen
    • Arbeiten mit dem Webviewer
    • SQL Anfragen in FIleMaker oder an andere Datenbanksysteme
  • Zeit für Fragen
Anmeldung bei mir. Kosten 99 Euro + MWSt. inkl. Mittagessen und Kaffeepausen.
Bitte Umsatzsteuer ID angeben bei Anmeldung.

Oder melden Sie sich bei der Denkform an für den MBS Workshop am 2. März und 7. Dezember 2017 in Hofheim (Taunus).

MBS FileMaker Plugin, version 7.0pr4

Thursday 19 January 2017 at 9:51 pm
New in this prerelease of the 7.0 MBS FileMaker Plugin: Download at monkeybreadsoftware.de/filemaker/files/Prerelease/ or ask for being added to the dropbox shared folder.

FileMaker DevCon 2017

Thursday 19 January 2017 at 7:46 pm

See you in Phoenix Arizona for the FileMaker Developer Conference, 24th to 27th July 2017.
The ticket price is down to $899, but you also get only 2 conference days plus a day for keynote and/or training. Hotel $149/night.
FBA members get an extra day.

Field Colors in FileMaker via other field and Xojo app

Thursday 19 January 2017 at 11:21 am
There was a question on how set field background color in FileMaker based on a color in another field:

So we define a field which gets a color using formatting rules. The other field defines the hex color code to use. To keep it smaller, we only allow 4096 colors: Those where the two digits per color channel are equal. So from 000000 to FFFFFF with steps of 11. e.g. put FF0000 here to make field background red.

To generate the conditional formatting rules, we use a Xojo app:

The workflow is like this:
  1. Cut or copy a field in layout mode in FileMaker.
  2. Go in the app and type the right field name for the condition.
  3. Press the button to add formatting rules.
  4. Paste field in layout with colors.
Please try it. To change/build the Xojo app, please download Xojo on the Xojo website. For just running the project with your custom modifications in the IDE, you won't need to buy a license.

Download test database and project here: FieldColor.zip

FileMaker Pro 15.0.3 Update

Wednesday 18 January 2017 at 8:00 pm
FileMaker Inc today released FileMaker Pro 15.0.3, an update to address bug fixes and various compatibility issues.

You can read in the knowledge base about FileMaker Server 15.0.3 (6 fixes),
FileMaker Pro (Advanced) 15.0.3 (6 fixes) and FileMaker Go 15.0.3

As usual FileMaker provides updaters only for Windows and we miss the ones for Mac. So here are the links for Mac:

FileMaker Advanced 15.0.2 to 15.0.3:

FileMaker Pro 15.0.2 to 15.0.3:

Be sure to only apply them when you have the right 15.0.2 version before and FileMaker is not running.

curl meeting in Germany, March 2017

Tuesday 17 January 2017 at 8:26 pm
On the weekend of March 18-19, 2017, the first ever curl meeting is taking place is Nuremberg, Germany.

Users, developers, binding authors, application authors, curl maintainers, libcurl hackers and other people with a curl interest are welcome!

I will try to be there and finally meet the curl people. I've been using curl for various projects including Xojo and FileMaker plugins for over 10 years.

MBS FileMaker Plugin, version 7.0pr3

Friday 13 January 2017 at 5:18 pm
New in this prerelease of the 7.0 MBS FileMaker Plugin:
  • Changed Audit: CurrentTimeStamp, CurrentTime and CurrentDate. Those can now be TimeStamp, Time, Date instead of Text fields.
  • Changed Audit: FieldID, TableID and RecordID can now be number fields instead of text fields.
  • Fixed progress dialog updates for macOS Sierra with CURL synchronous upload.
  • Fixed an issue with PrintDialog functions and Mac OS X 10.6.
  • Enabled script colors for German script editor for FileMaker 13 (broke in 6.5).
  • Added PrintDialog.GetReset and PrintDialog.SetReset.
  • Added progress window option to Files.CopyFile and Files.MoveFile for Windows.
  • Changed SQL plugin to detect ODBC to FileMaker and handle that better for reading text fields and avoid a crash.
  • Added enable parameter FM.AllowFileDragDrop, so you can disable/enable it when needed.
Download at monkeybreadsoftware.de/filemaker/files/Prerelease/ or ask for being added to the dropbox shared folder.

Batch sending Emails in FileMaker via MBS Plugin

Tuesday 10 January 2017 at 3:40 pm

As you may know you can use CURL functions in MBS Plugin to send emails. We include examples to show you how to send with attachments, html text and inline graphics. A recent example coming with 7.0pr2 showed you how to batch send emails. But that example sends emails one by one and each time with a new connection. I already improved the example here to reuse connections which helps a lot on speed. Still the big problem is that network transfers with uploads take time. The script waits while the Kilobytes for the email go through the network cables. 


Background processing


Luckily our plugin offers a function for cURL to run a transfer in background: CURL.PerformInBackground. Using this function we can start a cURL transfer and the script continues. We can prepare and send the next email while the last one is still uploading. Now you need to be careful and manage the connections and their status. To show you how this can work, we show you what we did in our updated example. Here is an excerpt from the script where we look for a free cURL session: 



#Find a non busy curl connection

Set Variable [$index; Value:1]


If [$curls[$index] = ""]

#found free index, setup new CURL session

Set Variable [$curl; Value:MBS("CURL.New")]

Set Variable [$curls[$index]; Value:$curl]

Set Variable [$r; Value:MBS("CURL.SetOptionURL"; $curl; "smtp://" & $SMTPServer)]

Set Variable [$r; Value:MBS("CURL.SetOptionUsername"; $curl; $SMTPUser)]

Set Variable [$r; Value:MBS("CURL.SetOptionPassword"; $curl; $SMTPPass)]


Exit Loop If [1]


#found used index

If [MBS( "CURL.IsRunning"; $curls[$index] ) = 0]

#found used index which is done

Perform Script [“HandleFinishedCURL”; Parameter: $curls[$index]]

Set Variable [$curl; Value:$curls[$index]]

Exit Loop If [1]

End If

End If

Set Variable [$index; Value:$index + 1]

If [$index = 9]


Set Variable [$index; Value:1]

Pause/Resume Script [Duration (seconds): ,01]

End If

End Loop



Xojo job offer in southern France

Monday 09 January 2017 at 5:48 pm
MedinCell S.A. is a company located in Montpellier in southern France near the Mediterranean Sea.
They use my plugins for a few years now and are looking for another Xojo developer: (more)

Allow file drag and drop from FileMaker container field to Finder

Monday 09 January 2017 at 2:40 pm
On the weekend we run into the issue that you can store files in a container, but you can't simply drag them into other applications or to the Finder.

To enable the desired behavior with a new plugin function called FM.AllowFileDragDrop.

The plugin than intercepts the drag and drop in FileMaker and writes the data into a temp file, so the drag includes a file reference and does work with Finder and other applications.

Watch the video: AllowFileDrag
Requires MBS FileMaker Plugin 7.0pr2 plugin or newer.

MBS FileMaker Plugin, version 7.0pr2

Monday 09 January 2017 at 11:12 am
New in this prerelease of the 7.0 MBS FileMaker Plugin: Download at monkeybreadsoftware.de/filemaker/files/Prerelease/ or ask for being added to the dropbox shared folder.

FileMaker Conference .fmp[x]Berlin 2017

Saturday 07 January 2017 at 3:09 pm
Registration just started for the FileMaker Conference .fmp[x]Berlin 2017.

This conference is organized by Egbert Friedrich and takes place from 1st to 3rd June 2017 in Berlin, Germany.

As the conference is in english, this is your chance to meet people from around the world at a conference in Europe. And for a lot of people it's easier to get to Berlin than to cross the atlantic and deal with US immigration officers.

dotfmp is an effort of various leading European FileMaker Developers. It is meant to bring all kinds of higher level developers together to share knowledge, educate and challenge each other.
dotfmp starts at the 31 May 2107 in the later afternoon with a relaxed "Beer and Sausages" in one of the most famous Berlin Beergarden.The session days itself last from 1 until 3 June with various socialising events in the evenings. Additionally we offer suport on 4 June to see more from Berlin and its surroundings.
dotfmp is a 3 Day-Unconference, Meetup, Hangout or Barcamp. It is an informal and self-organized effort to meet on a personal base.
dotfmp takes place in one of the most famous spots in Berlin. The GLS Campus is located in a vibrant area with a very short walking distance to all the famous restaurants.
We feel there are far too few possibilities to talk to, learn from, and hangout with fellow developers in a relaxed and informal environment. And we'd like to share work and get feedback from people chewing on similar challenges.

If you like to join the conference and present something, please register soon.

FileMaker Stammtisch SaarLorLux

Saturday 07 January 2017 at 11:04 am
Next Thursday, 12th January 2017, I will visit the regular FileMaker meeting in Saarbrücken.

If you like to join us, please sign up on the website filemaker-stammtisch-saarlorlux.de.

Feel free to ask me about our MBS FileMaker Plugin. Or lets talk about upcoming conferences?

Audit with MBS FileMaker Plugin

Saturday 07 January 2017 at 12:11 am
How FileMaker Pro can log changes

Since 2012, the MBS plugin has an audit functions. With version 6.5 they got much faster and therefore you may want to take a closer look on our audit functions. In FileMaker Pro, you can use them to easily log all changes to the database. Later you can inspect who changed records and use the log to undo actions or display old values.

Audit with MBS

We start with a test database. For the example, we take the starter solution called event management. The audit function need an AuditLog table and a matching layout. Both of these should be available somewhere and can be in a different database. The MBS plugin looks into the AuditLog layout to determine which fields should be written. The records are then written internally using SQL commands. Therefore, there must be only a relationship to an AuditLog table, even if it is located in a different database. This is quite interesting for server-based solutions, if the log is split into several AuditLog tables and the relationships define which table logs into which AuditLog table.

We add fields to the AuditLog table. The following fields are required: FieldName, FieldHash, TableName and RecordID. The name for the field and the table define the field exactly. We know which record was changed via the RecordID and FieldHash is then the hash of the field value. The field value can be very long and can, but does not have to be written down.

The following fields can be defined:
FieldValue, FieldOldValue, FieldType, UserName, IP, CurrentTimestamp, TimeStamp, CurrentTime, CurrentDate, Action, CurrentHostTimeStamp, PrivilegeSetName, AccountName, LayoutNumber, ApplicationVersion, FileName, HostApplicationVersion, HostName, HostIPAddress, LayoutName, PageNumber, LayoutTableName, TableID, FieldID, ScriptName and WindowName.

In FieldValue, the plugin saves the new value. In the FieldOldValue field, it saves the old value of the field. This is, of course, only available if the plugin finds the older entry. FieldType saves the type of the field, for example text. UserName saves the user name and AccountName the current account name. The CurrentTimestamp, CurrentHostTimeStamp, TimeStamp, CurrentTime, and CurrentDate fields store all the current time and/or current date. Hostname and HostIPAddress define on which computer the change was made. LayoutName and LayoutNumber which layout was used, WindowName which window. TableID and FieldID store the IDs for the table and the field. Later you can then find values by IDs even faster.

Create an Audit table

So let's put a table called AuditLog and the fields FieldName, FieldHash, TableName, RecordID, FieldValue, FieldOldValue, FieldType, UserName, IP, CurrentTimestamp, Action, FileName and LayoutName. We also add an additional field to EventID. Because we can always save the ID of the event and then find the changes for an event. FileMaker automatically creates a layout for the new table. This layout is required by the current plugin to find the fields in the table. We can later see in the layout what was logged. Of course, regular users may not need to see the audit table or the layout.

You can create additional fields in the AuditLog table. For example, a LogTime field with the data type time stamp for the current time of logging. This field can automatically be filled by FileMaker. You can also pass these additional fields later using an audit call, for example, to log a variable.

Audit fields

In each table, we create an AuditTimeStamp field. This field is automatically set by FileMaker to the current time stamp when the record changes. If you already have a field with a different name, you can also use it and do not need a field with a redundant time stamp.

We also create a second field called AuditState. This will be a calculated value, which needs to be recalculated each time. So please uncheck the "Do not replace existing value of field" checkbox. The calculation is the call to Audit.Changed. This function has several parameters. First, we pass our time stamp, behind the name of the table itself, in this case events. Then we can specify fields that should be ignored. We can also use field name and | as a separator to fill a field with a given value. So, we set the value of the EventID field to the value of the EVENT ID MATCH FIELD field. Finally, we pass the label from the field "Task Label Plural" as this field should not be logged. This field is calculated easily from the other fields. Thus, the audit call looks like this:

MBS ("Audit.Changed"; AuditTimeStamp; "Events"; "EventID|" & EVENT ID MATCH FIELD; "Task Label Plural");

For the other tables, the calls would be:

MBS ("Audit.Changed", AuditTimeStamp, "Contributors", "EventID|", & EVENT ID MATCH FIELD)
MBS ("Audit.Changed"; AuditTimeStamp; "Tasks"; "EventID|" & EVENT ID MATCH FIELD)
MBS ("Audit.Changed", AuditTimeStamp, "Agenda", "EventID|", & EVENT ID MATCH FIELD)
MBS ("Audit.Changed", AuditTimeStamp, "Guests", "EventID|", & EVENT ID MATCH FIELD)

So the plugin logs all the changes for the events. You can open the windows side by side, one with the events layout and one with the layout for the AuditLog table. For changes to the portals you have to click on a free space in the event to write the changes to the record. This writes the changes for all portals together. In the AuditLog, we see many new entries for the new records.

Positive or negative?

There are two Audit.Changed commands in the plugin. Audit.Changed takes the field names that are not to be observed. On the other hand, Audit.Changed2 is different and takes a positive list of fields. Basically, Audit.Changed2 is faster because it does not have to query which fields are available. Form fields or unsaved calculations are not monitored by default, since these are easy to recalculate.

With the Audit.SetIgnoreCalculations function, you can completely disable the monitoring of all calculation fields. With Audit.SetIgnoreSummaryFields, you can ignore the summary fields. Or with Audit.SetIgnoreUnderscoreFieldNames all fields with underline at the beginning of the word. You can also use Audit.SetIgnoredFieldNames to globally specify a list of field names for fields that you want to ignore. by default the plugin ignores the AuditState and AuditTimeStamp fields.

Display the audit

We can display the audit data for the record. Perhaps not for every user, but the display is always useful as a change log. To do this, create a relationship between Events::EVENT ID MATCH FIELD and AuditLog::EventID in the relationship diagram.

Now create space in the event layout and create a portal for the AuditLog table. If it is not found in the reference records pop-up menu, you have created the relationship above incorrectly. You could sort the fields down by CurrentTimeStamp. It is enough to take the fields FieldName, FieldValue and perhaps UserName.

Audit on deletion

If you want to log the deletion, you have two options. Either you let the user delete only by script and you always notify the plugin before deleting, or you use the security settings in FileMaker for a delete trigger.

The call from the plugin would then be via the Audit.Delete function:

MBS ("Audit.Delete"; MyTable::AuditTimeStamp; "MyTable")

The time stamp is passed, but not really used. Instead of using MyTable, you specify the current table from the current record. The plugin logs the record as with the other calls, so all the changes to the fields if needed and then an entry for deletion. You can of course do this in a script shortly before the delete command (with variable set).

Test users

First we need a test user to delete. In the Security dialog, we create a new user. We create a new set of permissions for this user. Best way is to duplicate and customize the permissions from the data input. In the settings for the calculation, there is a pop-up menu for records in the upper left corner. There, select "Custom privileges ...". A suitable dialog appears, where you can set the permissions for each table. For each table, select "Limited ..." instead of Yes. A new dialog box appears for the calculation of the limitation. Here, please insert the plugin call, for example for the events table:

MBS ("Audit.Delete", AuditTimeStamp, "Events")

For testing, we are building a script called login. This script gets only one command: Re-Login [With dialog: On]. If everything works out, you can use the new script to log in again with the new user. There you create a new data record. Make sure you commit some changes. You will see the recording in a second window with the AuditLog table. If you delete the record now, the calculation will be executed and the record should be marked as deleted. Please note that FileMaker first performs the calculation and then displays a dialog. If the user presses Cancel there, the plugin has already set an entry and the record still remains undeleted.


Many plugin users use audit. Because FileMaker often stores changes, each database should have an audit. Easily a record is changed or deleted and no one knows later who has made what and why. In addition, you can offer an undo feature, if you can find what was previously in a field.

The table with AuditLog is growing quickly, because a record is created for each change. However, you can easily rotate the table, for example change it monthly. The AuditLog table and layout must be available only in an open file. Therefore, it is recommended to put the AuditLog table in another database file. You can even have different audit databases for different files and separate the log data. Thus, a table can log into an audit file and another table logs to another file. For this, however, the relationships must be true, so that under the name AuditLog is a reference in the relationships that point to the corresponding table. Those audit log tables have of course different names.

The whole auditing works at best, when the users don't know about it. If an employee then makes a mistake, a supervisor can undo the change. Or if the data does not agree, who has done what and when.

In version 6.5, we have significantly improved SQL statements for audit, so the new plugin is much faster in the network. For each change, we need to look for old entries in the AuditLog and see if the values have changed.
Give it a try!

MarkDown via HTMLViewer for Xojo and FileMaker

Wednesday 04 January 2017 at 3:25 pm
As you may know we have an example for FileMaker to convert from MarkDown to HTML via JavaScript library in a webviewer.
For a client I just converted that example to Xojo.

On Mac OS X it looks like this:

and for Windows:

This is using Internet Explorer on Windows and WebKit on Mac.

Both ways we load a local html file which contains two text areas in a html form. We fill the first text control with the input text, call a javascript function and read the output via the second form field. This way we can pass much more multi line text than we ever could through URLs.

Please try it. Will be included in next prerelease or if you need now, drop me a line by email.

SQLite Release 3.16.1

Wednesday 04 January 2017 at 11:34 am
There is an update to SQLite.

The new version 3.16.1 was released yesterday and I already updated plugins here.

3.16.x is faster, fixes a few bugs and has some new shell commands.

If you need a copy now, you can email me as usual.

FileMaker Magazin - MBS Artikel

Monday 02 January 2017 at 4:58 pm

For our German speaking users:

Wir haben die Artikel zum MBS Plugin aus dem FileMaker Magazin gesammelt hier online gestellt: FileMaker Magazin Artikel:

Wir empfehlen allen FileMaker Anwender ein Abo vom Magazin und den Kauf der alten Ausgaben. Das FileMaker Magazin ist eine excellente Quelle von Informationen, Anleitungen und Profitips.

MBS FileMaker Plugin, version 7.0pr1

Monday 02 January 2017 at 12:27 pm
New in this prerelease of the 7.0 MBS FileMaker Plugin: Download at monkeybreadsoftware.de/filemaker/files/Prerelease/ or ask for being added to the dropbox shared folder.

New XML Functions in MBS FileMaker Plugin

Tuesday 27 December 2016 at 5:53 pm
The last days I chatted with a FileMaker developer who had a need for some XML handling functions. So I added a few functions, first one to extract node names from an XML: XML.NodeNames. You pass in a XML and it can give you the list of node names in the first layer or if you want recursively all layers.

Next we got a function to get a subtree (XML.SubTree). So you may have a big XML with a smaller chunks and we can query nodes inside a bigger tree. This includes getting the nth entry like the nth record in a list of records.

The XML.ExtractText extracts the text inside an XML tree. So all text portions are returned as a list. You can first use the subtree function to get a part of a XML to only get a portion of the texts.

We got a few functions to handle attributes. XML.GetAttribute returns the value for the attribute.

Setting Variables

Now we got something special for FileMaker Scripts.

We parse an XML with the XML.SetVariables function, identify all nodes with text values and create variables for you automatically. The plugin sets those variables and returns a list of the names. Later you can pass the list to XML.ClearVariables to clear them for another run.

For example the script looks like this:

Set Variable [$XMLVariables; Value:MBS( "XML.SetVariables"; test::input; 1)]

Set Variable [$otherVariable; Value:1]

#See Variables in Data Viewer

Set Field [test::output; MBS( "XML.ClearVariables"; $XMLVariables)]

Set Variable [$someVariable; Value:1]

The test XML:
<?xml version="1.0" encoding="UTF-8"?>
<CreationDate>2016-11-23 12:34:56</CreationDate>
<Comment>Just a test.</Comment>
And in the debugger all the variables may look like this for a test XML:

So you can have an input XML, split the values into variables using our plugin and process them in your script. I hope this is handy for you. What do you think?
Plugin will be available soon. If you like to test today, you can email me.

Xojo Developer Conference 2018

Monday 26 December 2016 at 6:52 pm
Just in time for Christmas Dana posted a teaser for XDC 2018.

The question to be answered is where the conference will take place. Until the next newsletter (subscribe here) in January tells us, we can enjoy betting where it could be.

Austin is not easy to reach, but convenient for Xojo Inc. as they have a couple of people living there who won't need any airplane ticket. Houston for 2016 was similar easy for Xojo Inc. with just a few hours drive from Austin. Dallas could fill a similar role with a big airport and in drivable distance from Austin.

We know that it will be USA and probably somewhere with direct flights internationally.
I would expect New York, San Francisco, Boston, Miami and and a few others to be too expensive.
And with the list of direct flights available from Paris and Frankfurt, I would bet on Seattle.
What is your guess?

There is no XDC 2017, so if you like to join a conference before 2018, please consider our conference in Europe:
The MBS Xojo Developer Conference will take place 4th/5th May 2017 in Berlin, Germany. An optional training day is available.

Older blog entries:

2016-12-25 Merry Christmas
2016-12-21 Finally Apple allows iPhone to stay silent in pockets
2016-12-19 Windows Error Codes
2016-12-16 FileMaker Stammtisch im Bärenpark
2016-12-15 Goodies video from FMValencia conference
2016-12-14 FileMaker Conferences in 2017
2016-12-14 FileMaker Stammtisch im Bärenpark am Freitag
2016-12-13 Three weeks till year's end
2016-12-12 MBS FileMaker Plugin 6.5 for OS X/Windows
2016-12-10 Supporting 10 years of FileMaker with current plugin
2016-12-10 Reminder: Update policy
2016-12-10 MBS FileMaker Plugin, version 6.5pr10
2016-12-07 Hotels, Beds & Places in Berlin
2016-12-07 Custom function to optimize PDF in FileMaker via DynaPDF
2016-12-05 MBS FileMaker Plugin, version 6.5pr9
2016-12-03 Compliment from Swedish customer
2016-12-03 FileMaker Conference in Madrid
2016-12-01 FileMaker DevCon 2017 surprises
2016-11-30 FileMaker Roadmap
2016-11-28 FileMaker Stammtisch im Bärenpark


Jan 2017
Dec 2016
Nov 2016
Oct 2016
Sep 2016
Aug 2016
Jul 2016
Jun 2016
May 2016
Apr 2016
Mar 2016
Feb 2016
Jan 2016
Dec 2015
Nov 2015
Oct 2015
Sep 2015
Aug 2015
Jul 2015
Jun 2015
May 2015
Apr 2015
Mar 2015
Feb 2015
Jan 2015
Dec 2014
Nov 2014
Oct 2014
Sep 2014
Aug 2014
Jul 2014
Jun 2014
May 2014
Apr 2014
Mar 2014
Feb 2014
Jan 2014
Dec 2013
Nov 2013
Oct 2013
Sep 2013
Aug 2013
Jul 2013
Jun 2013
May 2013
Apr 2013
Mar 2013
Feb 2013
Jan 2013
Dec 2012
Nov 2012
Oct 2012
Sep 2012
Aug 2012
Jul 2012
Jun 2012
May 2012
Apr 2012
Mar 2012
Feb 2012
Jan 2012
Dec 2011
Nov 2011
Oct 2011
Sep 2011
Aug 2011
Jul 2011
Jun 2011
May 2011
Apr 2011
Mar 2011
Feb 2011
Jan 2011
Dec 2010
Nov 2010
Oct 2010
Sep 2010
Aug 2010
Jul 2010
Jun 2010
May 2010
Apr 2010
Mar 2010
Feb 2010
Jan 2010
Dec 2009
Nov 2009
Oct 2009
Sep 2009
Aug 2009
Jul 2009
Apr 2009
Mar 2009
Feb 2009
Dec 2008
Nov 2008
Oct 2008
Aug 2008
May 2008
Apr 2008
Mar 2008
Feb 2008
XML: RSS Feed XML: Atom Feed