My ST_Data file also keeps growing. New results can be discarded (blank list), but somehow some old test results keep hanging around. Using the build-in Metastock utility: the starting screen does not report any existent tests (see attachment), although the counting nr. of each new test keeps increasing (234, 235 etc.) and the pie diagram shows the presence of a high % of the disk as being used for storing analysis results.
Repairing the database with the MS acces repair tool or the tool of this forum (thanks) does not make the file substantially smaller (remains around 1 Gb) Which results in spoiling disk space as well as very long loading times (up to 5 minutes) of the systemtester in Metastock
When I try to use the Metastock "discarding old results" tool with the "discard older then" field set at 600 days, there is no problem. (But also no results i.e. the ST_DATA file remains as large as it was). When I lower that number of days for the discarding old results field to 300 (probably some old data are originating from around this period) I first get errors : ..........increase the MaxLockPerFile nr. in the register.
I had to raise the maxlockperfile nr. in steps to 400.000 to get rid of this error. But then I got the next error: insufficient temp. diskspace. (XP 1024 RAM, 6GB free diskspace and virtual memory raised up to 5 Gb.) The windows system monitor does not even comes near these memory numbers when Metastock produces this error.
I have to say and report here that I find it very annoying that this problem is not straight forwardly solved by Equis although reported 3 times. This forum shows that it is a wide spread problem and I always regarded Equis is a company with good aftersales service. A bug fix should have been available a long time ago. Emails on this subject are answered with what seem to be "canned" sentences form a problem solution database. These answers often not even come close to any comprehention of the problem discribed. One Equis employee has to be praised because she at least took the effort to send me the repair RAR files. When I reported back that the problem still existed: never heard a word again.
My guess is that when you delete a testsytem the results that are still present can't be removed any longer. Another possibility is that some rubbish remains behind if the system crashes the first time when the maxLocksPerFile. nr is exceeded because of a to large ST-DATA file. The standard registernr. for the MaxLocksPerFile nr. after Metastock installation is set at 185 (?).
Who can help me to remove all remaining analysis results manually as discribed previously in this thread or with a fine utility as was published here previously and then removing all analysis results but not the formula?
(PS when I use a clean St-Data file from a new installed version and replace the large file for this standard installation file, you loose all your own made systems but things are starting fine and fast. But sooner or later you get the same problem, also on other machines. So it must be a general Metastock bug)