FIX: Cache "Error When Renaming Existing Relationship"

Retired KB Content Disclaimer

View products that this article applies to.

This article was previously published under Q223322

SYMPTOMS

Renaming an existing relationship to a name that is 260 characters long and then trying to get the name of the target object results in the following error:

"The cached relationship collection does not match the repository database"

This error only occurs if the renamed relationship is part of a UNIQUENAMING relationship collection. In addition, the problem goes away if the new name is only 259 characters or less.

Back to the top

CAUSE

The engine was not taking into account the null character when setting its size for a relationship name.

Back to the top

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

This bug was corrected in Visual Studio 6.0 Service Pack 3.

For more information about Visual Studio service packs, please see the following articles in the Microsoft Knowledge Base:

194022 (http://support.microsoft.com/kb/194022/EN-US/ ) INFO: Visual Studio 6.0 Service Packs, What, Where, Why

194295 (http://support.microsoft.com/kb/194295/EN-US/ ) HOWTO: Tell That Visual Studio 6.0 Service Packs Are Installed

Back to the top

MORE INFORMATION

Steps to Reproduce Behavior

Start a new transaction.
Rename the relationship to a name with 260 characters.
Commit the transaction.
Retrieve the name of the relationship's target object.RESULT: Step 4 results in the error:
The cached relationship collection does not match the repository database.

Back to the top

APPLIES TO

Microsoft Visual Basic Repository 2.0

Back to the top

kbbug kbfix kbvs600sp3fix KB223322

Back to the top

Retired KB Content Disclaimer

This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.

Back to the top