Page History

Usage:
Memory_Services('KeyExists', ErrorMessageKeyID)

Comments:
Sets an error to the stack. This will automatically clear any existing error conditions first so this error will be the only one on the stack.

Returns:
N/A 

Usage:
Memory_Services('GetValue', KeyID, ErrorMessageNotExpired, ExpirationDuration)

Comments:
Adds an error to the stack. This will not clear existing error conditions first. It is intended to allow higher level routines to add more information to an existing error condition or simply to maintain an ongoing error log for some troubleshooting or debugging purposes.

Returns:
N/A

Usage:
Memory_Services('SetValue', KeyID, Value)

Comments:
Clears all error conditions and related information.

Returns:
N/A

Usage:
Memory_Services('RemoveKey', KeyID)

Comments:
Returns the most current error message.

Returns:
The most current error message.

Usage:
Memory_Services('CreateHashTable')

Comments:
Returns the stack of error messages. This will be @FM delimited.

Returns:
The stack of error messages.

Usage:
Memory_Services('ReleaseHashTable')

Comments:
Returns True if there is an error condition, False if there is no error condition. Caller will still need to use the GetMessage or GetMessages service to determine what the error is. The HasError service allows the caller to embed the Error_Services service call inside of a conditional statement like this:

If Error_Services('HasError') then
* An error has occured. Proceed accordingly.
ErrorMessage = Error_Services('GetMessage')
end else
* No error has occured.
end

Returns:
True if there is an error condition, False if there is no error condition.

Usage:
Memory_Services('GetHandle')

Comments:
Returns True if there are no error conditions, False if there is an error condition. This is the opposite of the HasError service and exists for improved readability.

Returns:
True if there are no error conditions, False if there is an error condition.