Internal Error 512

[fmgoto]

Hey, I wonder what "Internal Error 512" menas. Thanks, Fabio

[EViews Gareth]

It means something happened that shouldn't have. Could you provide details as to what you were doing when it occurred. It probably means you've found a bug.

[fmgoto]

Well, I was running some thousands OLS and storing their @r2, etc. in a table. Sometimes I store just those with a R2 >= k (e.g., k = 0.80). I get this quite often.

I thought that might have happened because I defined a table with more than one million rows. Or perhaps because I have erased a hidden file.

Thank You, Fabio

[EViews Gareth]

Are you getting this error on a save or an open?

[fmgoto]

Mostly when I open a workfile, specially those that are large (couple hundreds of Mb).

Sometimes I leave the code running about, say, some thousands OLS or VAR and keep saving every couple of hundred iterations (both the workfile and a table with output - with wfsave and table.save).

When I am back to work in the next morning, I get this error. Today, I just got "Internal Error 520".

[fmgoto]

I dont know if this is related, but what is this "~f1" file? It is just as large as teh original ".wf1" file!

[startz]

It's just the backup of the previous version of the workfile from the last time you saved.

[fmgoto]

Then, if I am running Eviews 6, I can delete the file, right? How about the 512/520 error?

It is quite annoying, for I have to leave the program running for hours and I might end up with an unreadable 500Mb workfile!

Thank You, Fabio

[startz]

Yes, you can delete the .~f1 file. Mind you, if EViews is misbehaving having an extra backup around might be a good idea. :)

[EViews Gareth]

I think we'd have to see it in order to work out what is going wrong.

Could you send us your program and data?

[fmgoto]

Gareth, sorry, but I can't post neither code, workfile or data.

But the code runs about one milliion VARs changing series (log, dlog, @pcy, etc.), lags, etc. and retrieving in a table object some key statistics (like @rbar, @dw and var01.c(i,j)).

Thanks, Fabio

[EViews Gareth]

Without the program/data it will be hard for us to diagnose precisely. At a guess, you're simply pushing the limits of what can be held in a table. You might contemplate putting information into multiple tables rather than one big one.

[fmgoto]

What is the limit of a table? One million rows?

[EViews Gareth]

Complicated question with no real answer, as it depends on too many different factors.