There is one item shown on the module and entity property windows that VO does not explicitly show. It appears when compiler options have not been set, in which case the "owning" item's compiler options are used.
Compiler options can be set as defaults in VO's System Settings dialog or at application, module or entity level. In the AEF the compiler options are only stored if they have been explicitly set. If you have not actually set the compiler options at a certain level then the options of those above will be used. Export Explorer shows the compiler options if they have been set. If they have not been set Export Explorer displays text saying that the options are inherited from above.
For example, if you don't set options for an entity, then the module's options will be used. Export Explorer will report that the entity compiler options inherit from the module.
If the module doesn't have explicit options then the application options will be used to compile the entity. If the application has not had explicit options set then the entity will be compiled using the default VO options. Unfortunately the default VO options are not carried around in the AEF, so if you don't explicitly set the app options the same code can compile differently on two systems depending on how the default options are set.
Application
There are six screens of properties for an application, as shown below.
Module
There are two screens of properties for a module, as shown below.
Entity
There are two screens of properties for an entity, as shown below.
