Thanks for the response, Lynn. The software was installed by someone else but I was unaware that using a named instance would create this issue so I wouldn't have known any better myself. I thought if you were working on the same box that had the database engine, you could always use local.