Object Editor dialog box - other functions

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Object Editor dialog box - other functions

In the Object Editor dialog box, you can do the following:

  • Close the Object Editor dialog box, by clicking Close.

  • Save the changes to the current class or instance, by clicking Save Object.

  • Open the MOF dialog box, which contains the managed object format (MOF) code that you can use to construct the current object, by clicking Show MOF. It is important to remember that the MOF code shown in this dialog box might not be identical to the actual MOF code that created the class or instance. The original MOF file might have comments and different formatting from text shown, for more information. see Managed Object Format

  • Run a schema query that shows the class from which the current class or instance is derived, by clicking Superclass.

  • Run a schema query that shows the child classes of the current class or instance, by clicking Derived.

  • Show instances of the current class, by clicking Instances.

  • Control how the class are updated, by using the Update type option. The following tables describe the two groups of option buttons that control the update process.

Update Type Meaning

Create only

Used for creation only. The save operation fails if the class or instance already exists.

Update only

Causes this call to update.

Either

Causes the class or instance to be created if it does not exist, or overwritten if it exists already.
Update Type Meaning

Compatible

Allows a class to be updated are no derived classes and instances for that class exist. It also allows updates in all cases if qualifiers are changed, such as the description qualifier. This is the default value for this option and is used for compatibility with previous versions of WMI. If the class has instances, the update fails.

Safe

Allows updates of classes even when there are child classes, providing the change does not cause any conflicts with child classes. An example of an update to this value is adding to the base class a new property that was not previously mentioned in any of the child classes. If the class has instances, the update fails.

Force

Forces updates of classes when conflicting child classes exist. For example, this value forces an update if a class qualifier was defined in a child class, and the base class tries to add the same qualifier in conflict with the existing one. In force mode, this conflict is resolved by deleting the conflicting qualifier in the child class. If the class has instances, the update fails.

For more information on WBEMTest, see COM API for WMI. Also see the Windows Management Instrumentation documentation at the Microsoft Platform SDK Web site