Office 2007 - omigod

I've been using Office 2007. Ugh. I have a headache. Heartburn too.

Maybe the new menu structure/ribbon thing will be worthwhile someday, but it'll take years for me to recoup the productivity loss from this transition.

It varies by application. Word was such a miserable product that the ribbon is a minimal hit. They appear to have made some stab at fixing Word's completely broken stye sheets, but the "themes" tool requires use of .docx (surprise!) and that's not practical. Maybe in 3-4 years.

Access appears to have been severely wounded by the ribbon. Does Microsoft really think there's a way to make Access pretty? It's a data hacking tool for heck's sake! The new Access has some nice Sharepoint integration, but I don't see anything else I like so far. They don't appear to have fixed the big problems with Access (inline functions don't return values, rather the cell contains a pointer to the function, and the links to tables are still absolute paths and break all the time). Excel, as usual, escaped the worst of it. Nobody dares touch Excel.

Then there's Outlook. Ye gads. It may be the worst of the lot. Damn ribbons - I need a 32" display now! There's only one good thing in the Outlook update (excepting Sharepoint integration) -- the category view no longer breaks whenever you sort on a field. That bug has been in Outlook for eons.

Only a monopoly could get away with something like this ...

Update 6/26/07: Some things look bad, but get better over time. The ribbon isn't doing this. Ctrl-F1 toggles ribbon display of course, but that only mitigates the mess. There's something called a "Quick Access Toolbar", it feels like it was added in a last minute panic. You can partly restore some basic usability by painfully configuring the QAT, including tediously ordering the list by clicking, incessantly, an up and down arrow. That's right, no drag and drop, clicking an arrow. Vintage 1989. If the OpenOffice team tries to emulate any of this stuff they're insane.

FTP connections via Finder: use ftp://username@foo.org

Another good TUAW tip:

TUAW Tip: Using FTP in Finder - The Unofficial Apple Weblog (TUAW)

This week, Apple posted a tip about using FTP directly from Finder. What Apple fails to mention in its tip is that whenever you connect via the Finder's Go -> Connect to Server option, make sure to include the user name in the ftp address. Don't connect to ftp://foo.org, instead, connect to ftp://erica.sadun@foo.org. Adding the user name fixes nearly all the connection problems that people write to me about. Instead of getting "The Finder cannot complete the operation because some data in (address) could not be read or written. (Error code -36)." an authentication window appears.

The model of username@ also works for smb:// and afp://

Messing with OS X icons

Preview has surprising abilities ...

Import your icons into Photoshop - The Unofficial Apple Weblog (TUAW)

Basically, the trick is to open the application's icon in Preview (as was pointed out in the comments, you can most easily do this just by copying it in the Finder and selecting "New from Clipboard" in Preview's file menu), then save it in Photoshop (PSD) format. Now you can open it in Photoshop and get access to the image for editing, including the alpha channel.

I've usually done a get info to see icon, clicked on it, then cmd-c then open in preview.

Use of the SUBST command to reduce breakage of Microsoft Access 2003 links - an esoteric hack for escaping DOS 2.1's "path trap".

Where to pass on these kinds of tips and techniques for working around Microsoft's kludgy applications? It's a bit of a puzzle since Microsoft's products have an unlimited number of oddities requiring an unlimited number of hacks. This is but one of the myriad ...

I posted this one to Microsoft's high quality Access queries newsgroup, and since I use this blog to keep track of things like myself I'll post it here too. It's probably too esoteric for anyone else though ...

Use of the SUBST command to reduce breakage of Access links

One of the great failings of the past 20 years of Microsoft's dominance has been the failure to implement good file system redirection. XP today is almost as dependent on absolute paths as it DOS 2.1. [1]

In the world of Access this manifests as broken links to external data sources. I use links very extensively in my data management work, a typical project may contains dozens of query files with links to dozens of data tables distributed over one or more drives. Any change to any path, including renaming a folder or file or moving a file, will break the links.

Access 2003 responds to a broken link by irreversibly breaking a query on first use. It doesn't matter if you don't save the query when you see it's broken, the query is now broken. (This may be fixed in 2007.) If you're careful you can use Linked Table Manager to repair the link before first use of the query, but if you foget you're in trouble.

Today I reinvented a workaround. I say reinvented because I found a single mention of it in this newsgroup from 1999 [2]. It worked then so I presume it works now. Seven years is long enough that I'll repost the technique.

The trick is that DOS 3.x's SUBST command still works in XP. Indeed, in XP you can apply a SUBST operation to path containing a drive letter mapped to a network share.

The result is a de facto partial indirection layer.

Assume I have a database file john.mdb in c:\work\fark\dbase\cpt.

I run this command: SUBST P: c:\work\fark\dbase\cpt.

Now I create a link from a query database to a file in john.mdb

The link will have the path P:\john.mdb

Now I move john.mdb to e:\dbase\cpt

I now clear the P: substitution and run: SUBST P: e:\dbase\cpt
my links will not break.

For more information on SUBST simply type SUBST /? on the command line.

Of course if Microsoft were to implement file system indirection, or even relative paths in Access links, this kludge would not be useful.

meta: jfaughnan, jgfaughnan, Microsoft Access 2003, indirection, redirection, link, linked table manager, 070620

[1] Mac Classic's greatest innovation was an absolute file identifier that provided indirection, one could move files around without breaking relationships. OS X, sadly, broke much of this, but OS X today still has quite a bit of indirection.

Indirection is a member of the interesting class of things that are as unappreciated as they are valuable. Nobody ever mentions file system indirection as the most important innovation of the early Macintosh, but I think it really was. Twenty years later XP is almost as much a "prisoner of the path" as DOS 2.1. Sadly, OS X has regressed, though it's still well ahead of XP.

Despite the nastiness of using a fully specified path name to implement data table links in Microsoft Access, I do have to say the "link to table" technique is very useful and has very impressive performance and reliability.

The future of SVG is ?

I was an old SVG fan way about 3 DCB1 (before the Dot Com Bust 1). I'd lost track of it over the past few years as it was eclipsed by Flash and by Ajax based non-standard solutions. Work questions made me look it over again recently. Somewhat to my surprise, the technology may not be quite dead. So if Apple and Google decide to be nicer to each other than, say, Netscape and Sun @ 1997, we might see SVG play some role on small low bandwidth computing devices. Like, say, the iPhone.

But what about, you know, the IE web? On the one hand Microsoft's Silverlight is going to crush Adobe's Flash, so Apollo and Flash are irrelevant. Similarly SVG can't play on the larger web without Microsoft, so SVG seems irrelevant on the IE web too. On the other hand Google can't cede this battleground to Silverlight. (Apple of course can't either, but in this struggle they root from the sidelines).

So will Google buy Apollo/Flash (and/or Adobe)? Or will Google embed SVG support in the Google toolbar and thus bring it to IE / Vista? Or bet on both horses, since either is safer than Silverlight? (Adobe's SVG plug-in was never relevant, so let's not even mention it.)

This will be interesting to watch ...

If anyone sees evidence that Google is going to put an SVG reader into their toolbar code please send a note to jfaughnan@spamcop.net. I'm curious!

Gordon's Tech - migration to new domain

I've now migrated my three primary public blogs to the domain kateva.org. False alarm, I had some imaginary glitches and switched back to the old url for now. I'll probably switch again in a few weeks because it does actually work including automatic feed updating through the '301 redirect'. Below are some notes I'll leave in for reference ...

Update: Well, that didn't go so well after all. The feeds don't seem to follow the migration, so if you move a blog the old feeds don't seem to work. I'll see if I can get some Google tech support help, but in the past they've been hard to work with.

Update 6/20/07: I was too impatient. A post to Google Groups (I didn't try Google tech support) received a very kind response from "wasted":

I don't use bloglines myself, but Blogger will use a 301 redirect on the blogspot address to go to the new custom domain, for everything including feeds. So any feedreader should follow the redirect...

And so it does. It just takes a bit longer to update than usual, and it follows the common bloglines behavior of showing an unread count of "10". Bloglines updates the URL as well. I did two roundtrips on my test blog and it works. I've switched back to the old urls (hey, I was justifiably nervous) but I'll switch them one at a time over the next few days. It's noteworthy that bloglines managed two roundtrips, a "301 redirect" is "permanent". (see also)

Clearing the Finder "Open With" contextual menu

Delete com.apple.LaunchServices.plist. For more, see - Mac OS X: Clearing the Finder "Open With" contextual menu