> > Yes I know the mechanics behind views. But the SQL statements of a
> > view must be stored somewhere in a data base table(s) and I suspect
> > it is that table(s) getting corrupt because when I open the corrupt
> > view (using IBManager) I get the following message:
> > frmViewView_2.frmData.DataSelectQuery:
> > Arithmetic overflow or division by zero has occured.
> > arithmetic exception, numeric overflow, or string truncation
>
> The SQL statement of a view is stored in a system table, and it's the
> same table that all your tables main definition(fields are in separate
> table) are stored in. So, if it would be that table that would be
> corrupt, then you probably would have problems accessing some of your
> tables. And, the SQL statement is stored in a text blob.

I've had the same problem with InterBase 6 and Firebird 1. I haven't
been able to figure out why it happens, even after close examination of
the system tables ... :-/

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com