|
PureBytes Links
Trading Reference Links
|
Ron:
Thanks for this information. It will save all of us a lot of trouble
installing V7.02 eod.
Lionel Issen
lissen@xxxxxxxxx
----- Original Message -----
From: <stocks@xxxxxxxxxx>
To: <metastock@xxxxxxxxxxxxx>
Sent: Friday, July 21, 2000 3:25 PM
Subject: Re: MetaStock 7.02 EOD
> Do the following before installation:
>
> 1. Backup your 6.52a Metastock directory.
>
> 2. Manually go through your list of custom indicators
> and verify that each of the formulas still work.
>
> 3. Manually go through your custom explorations and experts and
> verify that each of the explorations and experts will work
>
> 4. Manually go through your custom system tests and
> verify that each of the system tests will work.
>
> 5. Correct any problems found in steps 2 through 4 before
> installing the upgrade.
>
> 6. Install the upgrade in the c:\program files\... default
> location which is different from the c:\equis\ ... default
> for version 6.52a. This will allow you to export any
> custom formulas, experts, system tests, that you may have
> purchased or written yourself. You can then switch to the
> 7.02 version to import the data. I would recommend doing
> each one individually as it can help in resolving any problems.
>
> 7. If any of your formulas, experts, ..., etc have trouble with
> the conversion, hit the cancel button and then the continue
> button. This will force the conversion process to attempt a
> build of the object.
>
> 8. If you find corrupted experts (binary header file corrupted),
> touch each piece of the expert by adding a blank and then
> backspacing. Then push the OK button as this seems to re-write
> the binary header piecewise.
>
> 9. Verify that all experts, formulas, system tests, templates, and
> layouts were converted. I found problems in all the above objects
> during the conversion process.
>
> I think the problem is at least two-fold:
>
> 1. The conversion process expects all the formulas to be correct
> and resolvable. While it is true that you can not input a
> syntactically incorrect formula, it is NOT true that existing
> formulas are syntactically correct. This is especially true
> when nested formulas are being used and the formula names were
> changed but the calling function did not get the updated name.
> When you have several hundred formulas written over a period of
> 12 years, it is easy not to keep everything super pristine.
>
> 2. It appears that during the conversion process for experts and
> system tests that custom formulas were not in the lookup chain
> in some conversion cases. By using the trick in item #8, I was
> able to get the objects converted.
>
> Hope this helps.
>
>
> Ron Stockstill
>
> Note I have not completed the installation as I still need to get
> some templates and layouts converted.
>
>
>
>
> > At 10:03 PM 07/20/2000 -0500, you wrote:
> > >
> > >I have done further analysis and found 107 formulas did not convert
when
> > >moving
> > >from 6.52a to 7.02.
> > >
> > >I took the following action:
> > >
> > >1. I exported the 107 formulas using mswin6.52a organizer.
> > >2. I imported the 107 formulas using mswin 7.02 organizer.
> >
> > etc etc
> >
> >
> > Ron, others --
> >
> > Fedex just delivered my 7.02. Any suggestions or fresh advice from Equis
> > for avoiding these troubles in upgrading? I will backup before
installing,
> > of course.
> >
> > Thanks
> >
> > Chuck Engstrom
> >
>
>
|