Requesting Rates

Support

How do I know who has published a rate?

Include the fields 'Source' and 'SourceIP' in a request. The returned values will be the publisher's computer name and its IP address.

How do I know when a rate was last updated?

Include the field 'Timestamp' in a request. The returned value will be the date and time of the last change to the item. Note that is the time that ANY field of the data item was updated.

The requested values are showing '<WFR>'

<WFR> is the code for Waiting For Rate. One of the following applies:

The requested value has not yet been sent through: the RateShare server may be busy.
The requested item does not exist: there has been no value published for that symbol or field.
A connection could not be established with the server. This could be due to an invalid server licence - the server application event history should provide details.
The server has been shut down: restart the server or request from a different server.
There is a problem with the network.
The server is overloaded: try re-opening the worksheet with fewer requested items.
The actual published value is <WFR>.

The requested values do not update

Ensure that the RateShare DDE monitor (RateShareDDE.exe) is running. If not then restart Excel.

Publishing Rates

Err:Server Down: The specified RateShare server is not running. Start the server and try publishing again.
Err:Server Closed: The specified RateShare server is not defined. Select a server that has been defined with the RateShare Configuration Utility.
Err:Circular Reference: The source for the published value is the same value requested from the RateShare server .
Err:11022: The specified server computer could not be found. Check that the name or IP address is valid (the Windows network utilities, e.g. ipconfig.exe, can be used to check that the host name is correctly specified).
The published rate is followed by '(Delayed)': This suffix indicates the server is busy with several data requests. The published rate will not be distributed to interested users immediately, but after a noticable delay. This situation will cease when the load on the server is reduced.