At 10:18 PM 16-10-02 +0000, you wrote:

>--- In IBObjects@y..., "Martin D. Berezaga" <mdberezaga@y...> wrote:
> > Is there any vantage/disvantage on using a View instead the Join
>that forms
> > the View? I'm using my own Edit/Inser/Delete SQL (Stored
>Procedures).
>
> >From what I understand...
>
>Advantages:
>1) Views don't have to be prepared. So technically they are faster
>(initially).

All queries have to be prepared.

>Disadvantages:
>2) Views are not updateable in certain instances.

The same is true of joined datasets.

>But these are client-side issues... if all this is done within SPs,
>then there would be no difference.

Martin already said he was using custom xxxSQL.

The advantage of views is usually the security benefit, where a user's
access to certain columns of a table needs to be limited. GRANTs can be
made to the view without compromising the security of the whole table.

One recognised disadvantage of views is that their implementation in the
engine has never been free of a number of bugs. For sets involving
multiple complex joins - particularly between tables and views or between
one view and another - they should certainly be tested thoroughly to make
certain they generate the sets you expect.

Helen