Interesting story - the problems we are having now have to do with structural database problems. Originally, Invision thought that I took a 1.3 database and tried to use it with 2.0.2. But I insisted our old database was 2.0.2 as we had upgraded already. They tried working on it, but had no luck, and wrote me back again today telling me that it still looks like a 1.3 database. So, the problem may be, I backed up the wrong database. However, there's only one database on the server we're on. But...when we first upgraded to 2.0.2 and we couldn't get a lot of people online, they talked about moving our database to another server...so...maybe our database is sitting there on another Invision server and it hasn't been backed up, it hasn't been gzipped, and it hasn't been moved to the new server. Oh, what fun! So right now they're going to look into where my database might be living within the Invision server farm and if that's the problem, I should just be able to move it over (should take a day) and we might be up and running. If not, they're going to do extensive work on the database and who knows how long that'll take.