>Hello,
>
>I do not like so much to define the views in the DBC and to distribute the DBC.
>Because of this, I define the view always in code in the program. But the problem here is performance: it takes quite some time. So I would like to check whether it is necessary to update the view definition: Does the view exist, has the view definition changed etc.
>Especially whether the view exists I could not figure out in code.
>If this is possible, then I just create the view when it does not exist, otherwise I do not need to create the view. And in the upgrade procedures (with a new version) I create all views again.
>
>What is the syntax for checking whether a view exists?

I don't know why your view definitions should take long to run. Your only creating the definition of the view, not running the query for the view itself...or are you running the query?

FWIW, I always define my views in code, and keep them in a separate DBC, which I also create in code. I've never noticed any delay when the DBC and views are created.