Got it... $lastuser is being overwritten with a boolean when it should have the lastuser's id.

Line 31 should have this
$lastuser = $pms['userid'];

You are correct... Zip is updated and I checked it on a live board this time with real PM users ;) My Dev board has me, myself , and I and while there are three accounts we don't tend to PM each other much :p

Haha, sorry I threw that code together in a bit of a rush (just copy and pasted most of your old code which is how it still had query_first and not query_read), and forgot to add the other line setting $lastuser to $pms['userid']. Glad you all figured it out.

What's the whole problem we are talking about? What PM counter do u mean exactly, and how could it have a negative effect on your forums?

It is the PM count that shows in the header or in your profile... It could say you have 10 PMs when you have 3000 (or the opposite) and your PM limit will be based on that count! You can also have issues with the system sayingyou ALWAYS have 2-unread PMs... but they will NEVER CLEAR as you need to reed those unread PMs before the count will reset. The problem is, you don't have any unread PMs...

If you ever have the problem, you will know it as your members will complain!

I have never experienced problems with that to be honest..

I could have used this awhile back, some users had something like "62781287 unread messages." Only way to fix this (wrong) number was to empty their PM mailbox.

Thanks for sharing, Quarterbore!

Perhaps to quell concerns, this utility would be better served as a menu item available in the AdminCP, available under "Maintenance."

True... I actually have been trying to get this considered for an addition in vBulletin itself (they can recode as they would like) and I have posted this over at vBulletin.com as a suggestion for inclusion. We will see...

Did u make a bugreport of it?