Serena,

System Tester has a major drawback. It's the file St_data.mdb stored at ...\equis\metastock folder. This file is the database where all buy/sell conditions (=systems) and system test results are stored. As it keeps growing each time System Tester is used, it impairs system performance, sometimes generating error messages as the one you have received.

When Metastock is installed a "clean" St_data.mdb file is stored at ...\equis\metastock folder. It is advisable to keep a backup of this original file. After some System Tester use replace the active St_data.mdb by this backup file, as follows:

a) Create a back up of your systems, through the export function,
b) Rename the "old" ST_data.mdb file as ST_data_old.mdb,
c) Copy the original "ST_data.mdb" backup file to ...\equis\metastock folder.
d) Use import function to reinstall your systems.

It's cumbersome, but works.

Nickless

Hi!

Thanks for the posts!

I've tried to delete se_data.mdb and reinstall Metastock, after.

But it didn't work. Again, had a crash after few seconds test.

Some other ideas?

Again, thanks for the interest and for the help.

When I get the crash, I’m doing nothing, besides the test itself.

Error occurs just few seconds after test begins.

A detail: if I perform a short simulation with up to around 200 tests, runs OK.

Running a customized test, but I’m almost sure this troubled is related to my hardware or software, instead of customized System Test, since I’ve installed Metastock in another machine for a test and that worked OK.

Comparing configuration, where first PC is the test one, that runs without any trouble and the second my major machine, where have the error just few seconds after test begins:

Processor: 1) Pentim 1500 x 2) AM2 64 X2 3800

RAM: 1) 256MB x 2) 1GB

HD: 1) IDE 40GB with FAT 32 x 2) SATA2 160GB NTFS (could archives system be related to the problem?)

MS Office version: 1) Office 2000 x 2) Office 2007 (could Office version be related to the problem, since Metastock uses an Access format archive, to perform some test operations?)

Best Regards,

Serena

Serena,

I have two computers one Pentium IV Dual Core (the newest) and one old AMD 2800. Curently i use Metastock v8 but i also have Metastock v9 and 7. When i first bought my Pentium (last summer) i have installed meta9 because at the time that was the version i used and it was installed also on my AMD on wich worked smoothly. However on my new Pentium when i did a exploration wich did required intensive computing Meta9 had the same error that u mentioned while on my old AMD worked without problems. Now i am using v8 because it runs smoothly on both machines and don`t ask me why Meta9 has "encountered a problem and need to close" on my newest and more performant Pentium IV Dual Core while worked on my old AMD 2800 without problems both computers having the same programs installed. So

I’ve installed MS 9 again, after uninstalling and removing registry entries, but didn’t work.

Same error on System Tester, after

Can you try opening/running the System Tester with an integrated browser opened first? Click File-->New-->Browser, then go into the Enhanced System Tester and try running your simulations again.

It is possible but I do not believe it is McAfee. If you are starting with a clean system though, it certainly wouldn't hurt to try putting MetaStock on first and running a system test.

Which version of Windows are you using? When exactly does the error message appear? Are you running on Local Data or Data on Demand? Are you running a single system test or multiple system tests? Are you testing multiple securities? Can you try testing the Sample folder?

Just to clarify, you did attempt to run a simulation with an integrated browser open? (File-->New-->Browser)

If so, the next thing you may want to try is running the MDAC Component Checker provided by Microsoft at:

http://www.microsoft.com/downloads/results.aspx?pocId=&freetext=component%20checker&DisplayLang=en

When you run the component checker, you must Perform Analysis Against a Selected Version of Windows - For Windows XP SP2 this should be MDAC 2.8 SP1 on Windows XP SP2

After running the scan, you will have a list of results with + signs next to them on the left-hand side. Click on these + signs and make a note of any MISMATCH items that show up.

Yes that is what to look for. Were there any other MISMATCH values that you noticed?