At 04:17 PM 19/01/2003 +0000, you wrote:

>When I define a view and triggers on it, and I do not want default
>action to take place, I use workaround mentioned here earlier - join
>with rdb$database (or "distnct" - anything to make view read-only).
>Everything goes fine until one happy moment when I receive "the
>object of the insert,update or delete statement is a view for which
>requested operation is not permitted. cannot update read-only
>view '...'".

Do you by some oversight include the FOR UPDATE clause in one or other of
the view spec or the query output spec?

Help us to help you, by providing enough detail for us to analyse your problem.

>There has been a lot of posts on this subject, but still no solution;

There have? It's a new one to me...

>moreover, I get this message when I try to SELECT from this view or
>any other dependent on it! I can somehow overcome this trying to
>select from independent views and then again from dependent, but when
>I close connection and connect again, the error repeats. It has
>become a nightmare - I can't do anything: simple select, metadata
>change, backup - all throws error!

It certainly seems like a metadata problem.

>Anybody knows the cause

No.

>and workaround?

Crystal ball? magic wand?

>Please help me, cause the DB is simply not working at all!

So give us some information and let's try to get it sorted. As a minimum:

:: The exact DDL for the tables upon which the view is based, and any indexes
and table triggers
:: The DDL for the view specification and any view triggers

:: The SQL for the query specification, exactly as it is when it crosses
the API

:: The parameter values that cause the error message

:: The client environment in which the error occurs

regards,
heLen