|
PureBytes Links
Trading Reference Links
|
For any of the persistant MS to MS OLE problems, I can only suggest not to
use the SAVE AS as Smart Charts file type Option that is given, but to create
fresh new standard Charts and then to SAVE AS as Charts. It will then
automatically also be saved as Smart Charts(if this option is applied in the
Programs' Options), but since this is also a special Metastock feature
(the "Smart" part), I cannot oversee what influence or effects this has/will
have on programs' own "real" Smart Charts.
They (the Smart Charts) are also used as being a different file type, obviously
then more extended loaded with the smart "luxuries" features, and files get
written to with these extra luxurious "smart" contents for the compilers to
interpret.
One thing to know also is, that Smart Charts(like Templates and standard Charts)
are also already linked(as some kind of Smart layout) to the securities held in
the MS Data Files.
So, suggest to create and put the to be OLE linked Chart(standard version but
having the Programs Option "Use Smart Charts" applied), into their own working
folder, then to link these Charts to their consequtive Smart Charts(usualy have a
number "in their name", but that is here irrelevant, unlike in Excel), or to link the
Smart Charts to their consequetive Charts, and then to test these method(s).
As to the Excel to Ms question:
Note that the to be linked indicator dates will have to match the base security's
dates, at least to guarantee proper OLE link outcome results.
Suggest to Link the base security's dates to Excel first, have the Excel indicator
streamlined with these dates, and then to Link the Excel indicator to MS. This
way, tho, requires for both the files to be Opened, eg to get updated simultaniously.
Also a CSV layout(comma's in seperate columns or used in the cells properties)
being used in Excel might be preferable and keeping it down to one or two
columns as well (see further MS-Manual p. 11+13).
Otherwise in Excel Selecting, Copying and in Metastock Pasting Special
as CSV in a freshly new created Inner Window(from the WorkMenu's Window)
and later to SAVE AS as Chart, will not give major problems.
Updating will then be automatically done when you Open the Chart(or both the
Chart and Excel files should you choose to use the base security link above).
Regards,
Ton Maas
ms-irb@xxxxxx
----- Original Message -----
From: rudolf stricker <rst@xxxxxxxxxxx>
To: <metastock@xxxxxxxxxxxxx>
Sent: zaterdag 6 maart 1999 13:45
Subject: Re: permanent DDE links: How?
>On Sun, 28 Feb 1999 21:46:12 +0100, you wrote:
>
>>Dynamic Data Exchange - DDE
>>
>>A way of communication between processes, implimented in the Operating
>
>[...]
>
>>Object - OLE
>>
>>A component that is recoqnisable for the operating system and user and can
>>only be made distinguasable by
>
>[...]
>
>>As to your burning question, suggest to create single seperate Charts
>>only(OLE use) and/or use the Smart Charts for
>>Layouts(Internal use).
>>Both ways, the links are then definitly stored in the consequtive Chart or
>>Layouts files (MWC+MWL) on disk.
>
>Thank you for your extended material on DDE & OLE. (Unfortunately,
>because I'm a WIN user since V1, I used the "ancient" shortcut "DDE"
>instead of the correct "OLE").
>
>But the problem is still there (c.f. my original posting): Even if I
>follow the correct CUT&PASTE SPECIAL procedure and store my charts as
>SMART CHARTS (as usual), the links are often broken, when I open the
>chart again the next day. Sometimes it works for some days, but then
>the links have crashed again: they are no longer updated or may even
>show erratic behavior for the data transferred up to then.
>
>This behavior shows up only for OLE-connections from Metastock to
>Metastock. Links from Metastock to Excel are very reliable.
> (BTW: Can I also set-up links from Excel to Metastock for e.g.
>single indicators calculated in Excel? Up to now I have to use this
>inconvenient import procedure via DOWNLOADER CONVERT several times per
>day.)
>
>mfg rudolf stricker
>| Disclaimer: The views of this user are strictly his own.
|