Ensign Wed Class -

Symbol Properties Window

March 17 , 2007

18:00 @Buffy2: I would like to understand the symbol properties window better. If a user is in Europe should the time zone be theirs or the exchanges. Is there anyway there can be a Q&A for the right way one should be setup for these?

18:01 Ensign Howard: Keep the symbol properties table on the zone for the exchange.

18:02 Ensign Howard: This is because we consult the zone selection of the symbol properties to know whether this symbol does or does not participate in a Day Light Savings. Some markets like Hong Kong never have Day Light savings, and others like Australia are opposite the US markets

18:03 Ensign Howard: So if a user in Sydney were to change our US symbols like ES to be a Sydney zone selection then our program is now confused thinking the opposite about when the ES is on and off of Day Light Savings.

18:04 Ensign Howard: It need to be a Pacific, MTN, Central or Eastern (ie a US zone) so we know it is on DLS from 03-11-07 through 11-04-07. So for Europe exchange symbols, have the zone be London or Berlin. They are not on DLS yet.

18:06 Ensign Howard: US market symbols need to continue to have a US zone selected so we know which set of DLS dates to use. Program knows about Europe DLS, US DLS, and Australian DLS dates. Our clue as to which apply to a symbol is the zone on its Setup | Properties form.

18:04 @Buffy2: Any chance of a data base of these symbol windows for foreign markets?

18:09 Ensign Howard: buffy, I think the symbol properties table we distribute on initial install is pretty good. If they have really messed things up there is a way to revert back to the original install file on the Setup | Charts | Maintenance form

18:10 @Buffy2: That takes all the windows back to original right?

18:10 Ensign Howard: Yes, it is task #11 on the Maintenance form. My master table has lots of entries for foreign futures My table is not complete, but defaults kick in for any symbol not listed. An example for the symbol might be in the Q&A knowledgebase too.

18:10 @Buffy2: Thank you