Good.. it IS possible it was an issue on Facebook's end... I know they have been doing some strange changes to how the search returns results (for which I added a workaround in build 55) and maybe they broke someting else while mucking about with that? I dunno. I try to make my software as robust as possible, but it's pretty hard to know what kind of errors various sites may decide to return in various conditions, there isn't like there is a magic "test mode" where I can force facebook to throw errors at my app for testing. (They should have exactly that, though, would help developers immensly) /Z