Last night was the Edinburgh meet up with Joel Spolsky, it was great to meet a few fellow software developers (and the occasional electronics/hardware/embedded software developer) who also think Joel’s articles are a great read. Although I seemed to talk to more Australian and New Zealand folk than I did Scottish, which is funny as I have often been accused of being from that area, and nearly moved there a few years ago, and it turns out Joel’s dad is from New Zealand.
So after the meet last night Joel and I we went for a nice dinner at Le Sept, just round the corner from the meet venue, whence my grilling of Joel commenced!
I thoroughly enjoyed the meal, we talked about all kinds of things related to software development, management, Fog Creek, FogBugz and other stuff. Joel’s a really nice guy, easy to talk to and very keen to share his knowledge, and also to help me out with CaseDetective where possible.
I hope Joel enjoyed the evening as much as I did.
Just a quickie to announce that CaseDetective 1.3.1 has been released; it includes a couple of bug fixes.
If you’ve had any problems in creating an extract or PDF file from certain filters because the “Save As” window doesn’t appear after the options window, you’ll want this release.
The issue was down to the default file name (filter name) being passed to the “Save As” window, if that filter name happened to have a “/” or other character in it that isn’t allowed in a file name, then the window simply failed to appear. The default file names for extract and PDF report files are now sanitised to only include alpha-numerics (a-z, A-Z, 0-9) and the space character, anything else is replaced with a hyphen. You can of course still change the file name once in the Save As window.
Thanks to Rosemarie for helping me find the cause of this problem with her wonderful debug log file, your patience and persistence is very much appreciated.
If you’ve had any problems with CaseDetective causing locking conflicts in your MS Access database, then you’ll also want CaseDetective 1.3.1.
I’ve only ever had one report of this problem, and it turns out it wasn’t actually CaseDetective causing the problem anyway, but CaseDetective has been updated to explicitly connect in read-only mode to any ODBC, MS Access and MS SQL Server database. It’s probably belts and braces and CaseDetective only does read-only operations on the FogBugz database anyway, but it can’t hurt as CaseDetective never updates the database.
That’s all folks.