|
PureBytes Links
Trading Reference Links
|
Tom, you export all of your systems tests before you replace the
ST_Data file and then after you replace it you import them. Once they
are imported you make a copy of tha new ST_Data file and put the date
in the name you assign to it as a backup. Next time you change the
ST-Data file you have to export the new systems tests that you've
created since the last ST change, but you don't have to export all of
them if you use the new backup.
If you can't get your ST_Data file small enough (under 10,000 KB) then
make a copy and edit it by hand using access. You can delete
everything except in the individual pages except the configuration
information on the last page called testoption.
Before you replace the ST file, delete all the systems test results,
go back to the clean page and recompress the file. That often gives
you a small enough ST file so you don't have to clean it up completely
by replacing it.
You can change the max locks per file by going to registry editor and
looking under software, microsoft, jet I believe. You'll have one or
two jet files. You'll see the max locks in there.
You can also do a search and find the file that way. I set mine to
250,000.
Technical support can walk you through the process if you don't know
what to do. However they think the max locks is in the equis file!
If you use Novell netware, you shouldn't set the max file locks higher
than 10,000.
I use Win 2000, but I've run MS using 98. I haven't had Harry's
problems. I use a gig of ram because MS does a lot of disk intensive
operations and swaps data around way too much which requires some free
upper memory. I think that might be the source of Harry's problems.
But it's only a guess. There's a lot of things that can make a
resource hog like MS hang up, especially memory conflicts and data
streaming collisions.
You can avoid those problems if you create a ram disk and store the MS
files in there. Then MS soars like an eagle.
If you're going to run a lot of systems tests you should look at the
RAM disk solution. You can find ram disk software by searching google.
You can read the pc magazine reviews of ram disk software. No big deal.
Have fun!
--- In Metastockusers@xxxxxxxxxxxxxxx, "Tom Sprunger"
<tlsprunger@xxxx> wrote:
> Harry,
> So you just have a small ST_DATA. mdb file that you replace the big one
> with.
>
> Are the system tests descriptions stored in ST_DATA.mdb?
> i.e. Do you lose new system tests when you replace with the older,
smaller
> file?
>
> Tom
> ----- Original Message -----
> From: "Harry M. Ward" <hmw3@xxxx>
> To: <Metastockusers@xxxxxxxxxxxxxxx>
> Sent: Saturday, March 12, 2005 12:30 AM
> Subject: [Metastockusers] Subject: Re: Re: Limitation for System
Tester???
>
>
> >
> > On 12 Mar 2005 02:31:39 -0000, "Tom Sprunger" <tlsprunger@xxxx>
> > wrote:
> >
> >>>This problem still exists on 8.01.
> >>>
> >>>I have to delete the results after virtually every system test.
Also run
> >>>the Cleaner/Compactor after every 4-5 runs. Even then every so
often I
> >>>have
> >>>to go in manually and delete the ST-Data file, and reinstall
Metastock.
> >>>Then it works great for a while.
> >
> > For Eric, and others who have not experienced this frustration, it is
> > related to an Access feature(?), MaxLocksperFile.
> >
> > The System Tester stores it's results in ST_DATA.mdb; a MS Access
> > file. For me, when this file get larger than about 70,000k (easy to
> > do, even with just one System Test), then one is unable to discard the
> > old tests, and will get a MaxLocksperFile error message, and/or
> > Metastock locks up. The only real solution, as Tom mentioned, is to
> > manually delete ST_DATA.mdb, and install a smaller version which you
> > have saved in advance, losing all calculated results. [Sometimes can
> > save the file by using MS Access recovery tools, but not very often]
> >
> > Going to the Windows Registry and increasing MaxLocksperFile setting
> > to over 100,000 has little, if any benefit, at least with Win98SE,
> > although some folks who have 2000 say it helps. My experience running
> > with Quick Test does not create any smaller files. So when I am
> > running the System Tester, I usually delete after every test. Not only
> > is this time consuming, but one must save the data outside Metastock
> > if you want to compare results.
> >
> > Another frustrating item that Metastock has knows about for a long
> > time, but doesn't seem to have enough interest to solve for it's user
> > base. Are you listening, Mr. Da Silva?
> >
> > Harry
> >
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
> >
------------------------ Yahoo! Groups Sponsor --------------------~-->
What would our lives be like without music, dance, and theater?
Donate or volunteer in the arts today at Network for Good!
http://us.click.yahoo.com/Tcy2bD/SOnJAA/cosFAA/zMEolB/TM
--------------------------------------------------------------------~->
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/Metastockusers/
<*> To unsubscribe from this group, send an email to:
Metastockusers-unsubscribe@xxxxxxxxxxxxxxx
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|