KB169333 - FIX: Engine: Collection Not Updated After Removing an Item

Article ID: 169333

Article Last Modified on 1/13/2001

Microsoft Visual Studio 97 Service Pack 3
Microsoft Visual Basic 5.0 Learning Edition
Microsoft Visual Basic 5.0 Professional Edition
Microsoft Visual Basic 5.0 Enterprise Edition

This article was previously published under Q169333

SYMPTOMS

If an item is removed from a unique naming convention collection you can not add an item with the same name on the following call.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This has been fixed with Visual Studio Service Pack 1.

For additional information about the Visual Studio 97 Service Pack 1, please see the following article in the Microsoft Knowledge Base:

170365 INFO: Visual Studio 97 Service Packs - What, Where, and Why

MORE INFORMATION

Normally, a name is associated with a repository object via a naming relationship. The collection for such a relationship provides the scope for the name and can require that all names in the collection be unique. This is the preferred method for naming objects when a given object will be the destination of only one naming relationship.

Steps to Reproduce Problem

Open a repository-based project that uses unique naming.
Remove item "X" from the collection.
Add an item "X" to the same collection.

Expected results:

Success.

Actual results:

Fails, item already exists.

Keywords: kbbug kbfix kbvs97sp1fix kbvs97sp2fix KB169333