A way to handle it would be to flag if the last message in a thread is not read... egarding those of us that work some days in one location and some days in another

Thanks for reminding me. I had forgotten that we had discussed making it "portable." That's the trick. It's not actually that difficult, but it's going to take a significant amount of database access and storage. Since it has to be portable, the information must be stored at 8052.com. That means the 8052.com database will have to be able to keep track of the last message read in each thread for each user. There are lots of threads and lots of users, so that's going to be some heavy-duty SQL access.

That said, I think the database is capable of handling it. I guess it's a matter of trying it.

I'll try in July.

Craig Steiner