Page 1 of 1

Database Error

Posted: Tue Feb 02, 2010 8:45 am
by javiersan
Hello,

I receive the following error:
"Database Error: database version is too old to support intraday data. Make a new database or use Proc->Copy on the existing data ..."

Although the message is self explanatory, the problem is that my data is on weekly frequency.

Regards,

Javier

Re: Database Error

Posted: Tue Feb 02, 2010 9:03 am
by EViews Jason
What was it you were attempting to do when you received the error?

Re: Database Error

Posted: Tue Feb 02, 2010 10:14 am
by javiersan
Store weekly data in the database.

Regards,

Javier

Re: Database Error

Posted: Tue Feb 02, 2010 4:05 pm
by EViews Jason
One of the new frequencies introduced in EViews 7 is Daily-custom week. One permutation of a daily custom week is a weekly 1 day week. Consider a weekly 7 day week but instead of 7 days constituting a week, only 1 day constitutes a week. EViews does not consider this frequency as weekly and therefore cannot be stored in older databases.

Can you verify your workfile structure/frequency (double click 'range')? In the frequency box, displayed should be either 'weekly' or 'daily -custom week'. If neither is listed, you have something other than a weekly frequency and it also may not be supported by older databases.

If 'weekly' listed then please verify EViews is up to date (Help->EViews Update) and then try again.

If 'Daily- custom week' is listed you will need create a new EViews database, copy all of the objects from the old database to the newly created one and then just work from the new one. If your workfile is structured in this manner, how did you create your workfile? Did you manually specify a custom week or did you import some data and EViews determined the structure for you?

A manually specified frequency is fine but EViews should not automatically determine 'Daily -custom week' as the frequency. If this occurred and if possible, please send a copy of your data to support@eviews.com.

Re: Database Error

Posted: Wed Feb 03, 2010 11:30 am
by javiersan
The problem was that the dates were not exactly weekly as the start date was 1 day off
1/6/2010
1/12/2010
1/19/2010
1/26/2010
2/2/2010

Thanks,

Javier