Sounds less like a bug and more like database corruption... of course it could be a bug that some action causes this corruption (a few days ago ALL my studio info became corrupted but I don't know how) so worth reporting, but it may just be a one off.

I am making sure I keep backups and copies of older backups just in case I get corrupt info that I don't notice for a while!

This has happened to me too (during the down time) and I did make a note of it

[the note]
I recently got the personalization bug which duped some personal data onto 4 other profiles (randomly I might add). If I recall correctly; I was trying to add a comment in the notes field for a profile that had child profiles. I used the right-click to access personalization window instead of double-clicking on the profile to go into edit mode. There seem to be a difference between the two possible choices. Anyway, the edit didn't take, so I tried 3 more times (unfortunately). And it was pure luck I did a sort on collection number only to discovered that 4 of my other profiles had got the personalization data from the master profile I was trying to update.
[/the note]

So my guess is;  right-click(on a master profile that has child profiles) -> Personalization -> Edit notes(or maybe some other personalization field) -> OK, will probably reproduce this error.

As you can imagine, I didn't want to test it a fifth time.

I do not recall exactly which profile it was that got changed, but I do remember that none of them was a master profile with children or a child profile.
I think the fields that got changed was "Purchase Place", "Purchase Price", "Collection Number", "Review" and "Notes".

Ken, I hope all that helps you some in fixing this bugger

Quoting widescreen forever:

Quote:
It's NOT a Bug! .,, What happened was you transferred over your 2.5 base to a 'saved folder' then updated that folder into 3.2 .., during the process you transferred over differanrt tags and what-not from the old base..

I did it myself a number of time last week, till I figured it out.

Sorry m8, I think it is, but I admit not being 100% about how to reproduce it.

and I didn't transfer anything during this ordeal and I have 2.4(probably doesn't matter) and TAGS was OK for the mentioned 4 profiles.