• assigns the name of the source knowledge base from which data and calculation results will be retrieved. The function returns 'true' or 'false' depending upon if the assignment was successful.
• returns the pathname of the currently assigned source knowledge base.
• creates and returns a new MKS Request object.
• causes the application to process the entered request.
• stores an error message within the application. Note that this error message may be replace by another message, automatically generated in subsequent code.

• returns the error message currently stored within the application object. Note that this returned string may be an empty string.
• assigns the window within which the Component Edition's dialogs will be displayed.
• displays the application's units conversion dialog. This dialog enables you enter a value in one set of units and have it converted to another set of units. Note that a display window must be set using the SetAppWindow function before the units conversion dialog can be displayed.
• returns information about the current application and its version.

• (required) assigns the type of processing the application should perform, e.g., 'Get Entities' or 'Get Units'. Processing the 'Get Requests' request type returns a response containing all request types.
• returns the request's assigned type.
• creates an entity, adds the entity to the request's internal array of entities, and then returns the new entity object. The returned entity's attributes can then be assigned values.
• returns the entity located at the given index within the request's internal array of entities. Indices are zero-based. This function returns 'null' if the index is less than zero or greater than the entity array's largest index.

• returns the number of entities present within the request's internal entities array.
• certain request types require additional arguments. This function adds an argument to the request and assigns it the input value. (Refer to the documentation on each request type below for details on required arguments.)
• returns the value associated with the input argument name.
• removes all arguments from the request.
• returns a string contains the application's name and version information.
• returns the error, if one is present, generated by the application during the processing of the request object.

• Hello: a simple request that returns some basic information about the running Component Edition application. This request type is very useful for initial testing of a client application. (see below)
• Get Request Types: returns all of the request types (i.e., the types described in this list) that can be currently processed by the Component Edition application. (see below)
• Get Entity Types: the Component Edition application processes different entity types, e.g., chemicals, mixtures, techniques, references. An entity's type typically must be specified when requesting data or estimates. This request type returns all entity types that can be currently processed by the application. (see below)
• Get Entities: returns the identifier, i.e., name, of each entity in the source knowledge base. An entity's identifier is required for requesting its physical property values. (see below)

• Get Properties: returns all the properties handled by the Component Edition application. These properties are typically required when making additional requests for data and estimates. (see below)
• Get Status Values: physical property values are categorized by their status type. For example, some values represent data values while others represent estimated values. A property's status value often must be specified when requesting data and estimates. This request type returns all status values processed by the Component Edition application. (see below)
• Get Values: returns the physical property values for a given entity. This is probably the most commonly used request type. To make this request, you must typically specify an entity's type, an entity's identifier, a property name, and a status value. Valid values for these inputs can be obtained by making the other requests documented in this list. (see below)

• Active: Values with an Active status are values that can be considered recommended by MKS. Constant properties will have only a single Active datum.
• Passive: Values with a Passive status are considered "good" but not the "best". Every property can have multiple Passive data.
• Estimated: Values with an Estimated status are values that have been previously estimated and are already stored within the source knowledge base. Typically, these values were estimated using the Professional Edition of Cranium or Synapse before the source knowledge base was deployed for use with the Component Edition. Note the datum's reference is the name of the estimated technique used to generate the estimated value.
• New Estimate: This status value instructs the Component Edition to generate a new physcial property estimate, even if one is already present in the source knowledge base. Note that the new estimate generated using this status value may be different than the estimated returned by the 'Estimated' status value. (This is becuase the estimate stored in the knowledge base, i.e., the value with the 'Estimated' status value, may have been estimated using a different estimation technique. Comparing the reference of this request's datum with that of the 'Estimated' status value request should show this difference.)

The 'Get Values' request is probably the most commonly used request type. To make this request, you must typically specify an entity's type, an entity's identifier, a property name, and a status value. To generate new estimates, you may also have to specify one or more datum values containing values for temperature, pressure, and composition.

Conceptually, you can think of a Get Values request as a form. You first add information you know on the form. You then submit the form to the Component Edition. The Component Edition returns the form to you with the missing information, or much of it, filled in.

The following examples demonstrate various Get Values requests.

For many requests you will need to specify some information about one or more entities. For example, to request a chemical's critical pressure data value, you must specify the chemical's identifier attribute. To request a mixture's estimated liquid density, you must specify the mixture's identifier and its list of components attributes. The entity object is used to specify such information.

• creates and adds an MKS Property Object to the entity's array of property objects. The newly created object is returned.
• returns the MKS Property Object at the indexed location in the entity's array of property objects. A value of 'null' is returned if the index is greater than the array's upper bound.
• returns the number of property object in the entity's properties array.

• returns the entity's assigned name.
• assigns the input value to the entity's name attribute.
• returns the entity's type, e.g., "Chemical" or "Technique".
• assigns the input value to the entity's type attribute.

• assigns the property's name. The Get Properties request can be used to retrieve a list of property names of a specific entity type and property type.
• retrieve the property's assigned name.
• assigns the status value of the property data being requested. See documentation on the Get Status Values request for an explanation of status values.
• returns the property object's assigned status value.
• certain physical properties of mixtures, e.g., the activity coefficient, fugacity coefficient, diffusion coefficient, and partial molar properties, are actually properties of the mixture's components. For example, a mixture containing chemical 1 and chemical 2 does not have an activity coefficient. Chemical 1 in the mixture 1 + 2 has an activity coefficient and chemical 2 in the mixture 1 + 2 activity coefficient.

  Thus to retrieve data and estimates for these mixture physical properties, you must use this function to set the component's index. Note that the component index is 'zero-based', e.g., in a binary mixture the component indices are 0 and 1.

  Only a few mixture properties are 'component dependent'. Thus, for most properties you will simply assign a value of 0.

• creates an MKS Datum object, adds the datum to the property's internal array of data, and then returns the new datum object.
• returns the datum located at the given index within the property's internal array of data. Indices are zero-based. This function returns 'null' if the index is less than zero or greater than the data array's largest index.
• returns the number of datum objects present in the property's internal array of data.
• typically, the Component Edition performs estimations in an 'automatic mode'. In this mode, the Component Edition examines input information, e.g., temperatures, pressures, and chemical structure, and then selects the best estimation technique. You can use this function to specify the name of the estimation technique that should be used instead of the one selected by using the automatic process.
• returns the name of the assigned manual estimation technique.
• returns the standard units for the property. Estimated values are returned in standard units.

When the Component Edition processes a 'Get Values' request it conceptually processes the request twice. During the first processing, the Component Edition temporarily stores all Active data found in the request object into the source knowledge base. For example, if the request has Active boiling point data, these values will be temporarily stored, or cached, in the source knowledge base. During the second processing, all other data and estimated will be retrieved.

This two step processing enables you to add values to the knowledge base, albeit temporarily, which can then be used in all subsequent estimations. The examples below illustrate the advantage of this approach. They both estimate the vapor pressure at 85C of 2-Hexanol. The literature value for this property is 11.466 kPa.

• returns the value of the number stored within the datum. Use the GetDValueUnits function to retrieve the units of this returned value. If no value is present, this function returns the value -99999 and sets the datum's error string to an error message. You may also use the HasDValue function to determine if a value is present.
• stores a numeric value within the datum. If you use this function to assign a value, you must also use the SetDValueUnits function to assign the value's units, unless the datum's containing property is dimensionless.
• returns 'true' is this datum has an assigned numeric value or 'false' if it does not.
• retrieves the value's accuracy (a positive number). Note that not every datum has an accuracy value. If no value is present, this function returns the value -99999 and sets the datum's error string to an error message. Is is thus important to check either the returned value or the datum's error, via the GetError function, to ensure a valid accuracy was returned.
• returns the units in which the datum's value and value accuracy are given.
• assigns the units for the datum's numeric value. You can perform a 'Get Units' request to retrieve a list of applicable units for the datum's containing property.
• datum's are often used to store string values. This function returns the value of the string stored within the datum.
• stores a string value within the datum.
• returns the datum's temperature value (a numeric value). Use the GetTemperatureUnits function to retrieve the units of this returned temperature value.
• assigns the datum's temperature at which the value was or will be determined. If you use this function to assign a temperature value, then you must also use the SetTemperatureUnits function assign a value for the temperature's units.
• returns 'true' is this datum has an assigned temperature value or 'false' if it does not.
• retrieves the temperature value's accuracy (a positive number). Note that not every datum has a temperature accuracy value. If no value is present, this function returns the value -99999 and sets the datum's error string to an error message. Is is thus important to check either the returned value or the datum's error, via the GetError function, to ensure a valid accuracy was returned.
• returns the units in which the datum's temperature and temperature accuracy are given.
• assigns the units for the datum's temperature value. You can perform a 'Get Units' request to retrieve a list of applicable units for temperature values.
• returns the datum's pressure value (a numeric value). Use the GetPressureUnits function to retrieve the units of this returned pressure value.
• assigns the datum's pressure at which the value was or will be determined. If you use this function to assign a pressure value, then you must also use the SetPressureUnits function assign a value for the pressure's units.
• returns 'true' is this datum has an assigned pressure value or 'false' if it does not.
• retrieves the pressure value's accuracy (a positive number). Note that not every datum has a pressure accuracy value. If no value is present, this function returns the value -99999 and sets the datum's error string to an error message. Is is thus important to check either the returned value or the datum's error, via the GetError function, to ensure a valid accuracy was returned.

• returns the units in which the datum's pressure and pressure accuracy are given.
• assigns the units for the datum's pressure value and accuracy. You can perform a 'Get Units' request to retrieve a list of applicable units for pressure values.
• returns the composition (a non-negative number) of the indexed component in a mixture. Use the GetXUnits function to retrieve the units of this returned composition value.
• assigns the datum's composition of the indexed component. If you use this function to assign a composition value, then you must also use the SetXUnits function assign a value for the composition's units.
• returns 'true' is this datum has an assigned value for the indexed composition or 'false' if it does not.
• retrieves the accuracy (a positive number) of the indexed composition value. Note that not every datum has a composition accuracy value for every component. If no value is present, this function returns the value -99999 and sets the datum's error string to an error message. Is is thus important to check either the returned value or the datum's error, via the GetError function, to ensure a valid accuracy was returned.
• returns the units in which the datum's composition values and accuracies are given. Although a datum may have several composition values, all values are processed using the units assigned by this function.
• assigns the units for the datum's composition and composition accuracy values. You can perform a 'Get Units' request to retrieve a list of applicable units for composition values.
• returns the name of the source of the datum's value. This source is typically a reference's identifier or a technique's identifier.
• assigns the name of the source of the datum's value. This source is typically a reference's identifier or a technique's identifier.
• returns additional information stored within the datum typically regarding the datum's value.
• assigns additional information about the datum. This information often documents the date and time of entry and details about the datum's value measurement or calculation.
• converts this datum's numeric value and accuracy from its current units into the input units. This function also assigns the datum's value units attribute to the new units. Note that the units conversion of datum's value may require a value for the molecular weight of the datum's chemical or the molecular weight of each of the datum's mixture components. The conversion will fail if a molecular weight is needed and the application cannot retrieve or calculate such a value.
• converts this datum's temperature value and accuracy from its current units into the input units. This function also assigns the datum's temperature units attribute to the new units.
• converts this datum's pressure value and accuracy from its current units into the input units. This function also assigns the datum's pressure units attribute to the new units.
• converts this datum's composition values and accuracies from their current units into the input units. This function also assigns the datum's composition units attribute to the new units. Note that the units conversion of datum's composition may require a value for the molecular weight of the datum's chemical or the molecular weight of each of the datum's mixture components. The conversion will fail if a molecular weight is needed and the application cannot retrieve or calculate such a value.
• returns the error message, if any, assigned by the application during the processing of this datum.