Saving Error Queue Information

A process can create multiple instances of the Repository class, with each instance connected to a Repository database. A repository database can have multiple repository instances connected to it simultaneously, from the same or from different processes. Each repository instance maintains a single, separate error queue.

You can access only one Repository error queue at a time. When you switch from one error queue to another, several things occur automatically:

• The IRepositoryErrorQueue interface reference to the first error queue is automatically released.
  
  
• If that reference was the only remaining reference to the interface, the error queue is destroyed.
  
  
• An IRepositoryErrorQueue interface reference to the second error queue is automatically added.

Consequently, if you switch from one error queue to a second error queue, and then back to the first error queue, the first error queue is destroyed and re-created as an empty queue.

To switch between multiple error queues and retain all error queue information

1. Obtain an IRepositoryErrorQueue interface pointer for the error queue.
   
   
2. Explicitly increment the interface reference count using the AddRef method that is associated with the error queue.

Note   You must repeat these steps for each error queue.

The error queues will be retained as long as you hold these explicit interface references.

To switch back and forth between error queues

• Use the SetErrorQueue method of the IRepositoryErrorQueueHandler interface. When the error queue information is no longer needed, use the Release method to remove the explicit interface references.