A database that I support was recently migrated from an R5 to a 6.0.2CF2 server. Since the migration, the profile documents have appeared in private views created from R5 clients. These are true profile documents because I verified they have the $Name field starting with $profile_. It seems that if someone opens the profile document from a private view, the data in the profile gets wiped out, causing major end user problems. I then recreate the profile using the normal @EditProfile method. I tried deleting all profile documents and recreating them, but the problem persists. I have also been able to recreate this problem in several databases on R6 servers. Has anyone else seen this problem?