We've got three people working together on a specification, and a master document in Word seemed like the way to go. Once I figured out how to do it in Word 2007's newfangled menus it was easy enough to set that up. (Go to View/Outline, and check out the Master Document section on the Outlining Menu.)

But when the files are uploaded to Project Server, I can't open the master document. Bummer. Looks like this wasn't supported in the past, but I can't find any specifics on the current versions.

I write about solutions to random computer problems here in the hopes that someone will run across them on Google and save some time. Here's one that would have saved me some time if I had written about it the first time I had to fix it.

I couldn't access folders with access restrictions on my Buffalo Linkstation from my new Vista machine. I had my user set up, and the multiple connections stuff didn't seem to apply.

I found this article that rang a bell for me. Vista has different ways of negotiating permissions over the network. Basically it doesn't use the old, less secure XP method, and the Linkstation doesn't support the new one. The steps in the above link (which didn't work for me, perhaps because I'm not logged in as administrator,) just change a registry setting.

Buffalo actually has a "patch" under the utility section of their downloads page (choose the linkstation option in the droplist.) This is just a registry key file which changes a single key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\LmCompatibilityLevel

Change the value from 3 to 2 and restart. Presto, explorer logs in with the current user and password, as expected. Assuming that this has previously been set up on the Linkstation.

I just found out that the canvas page URL for a facebook application is case sensitive.

So if the application is at http://apps.facebook.com/myapp, then the URL http://apps.facebook.com/MyApp will not work. Be careful when sending out links to your application!

I just got a new machine, and when I tried to load my website project to VS2008, I got a COMException from the conversion wizard for the web project.

I found some references to this - apparently it's caused by the user account not having access to IIS. The workaround was to run Visual Studio with administrative privileges, but this didn't work for me - presumably because I'm running Vista Home Premium, which doesn't have IIS installed at all.

My solution was to switch the project over to Visual Studio's built-in web server on another machine, check in the changes, then open it on my personal machine. If you're upgrading to 2008 on a single machine, I guess the solution is to switch over before trying to convert the solution.

I'm setting up the various versions of my facebook application and just discovered that the API key and secret strings don't have to correspond to the application!

The dev application can callback to a server that is set up with the security information from the production application, and facebook doesn't complain one bit. From facebook's standpoint these are two different apps, even if they have the same developer.

Since the developer(s) control the callback URL through the app configuration, I don't see a way to take advantage of this - or even a reason to have the keys to begin with. But why have them if they aren't enforced?