>>As mentioned this week, many people suggested to deal with views programmatically because of the limitations of the view designer.
>>
>>So, what I am doing is do create the view in the load of the form. However, to create a view, we need to have a database open. So, I create a database to hold this view. Now, what will happen if 2 users are accessing the form as the same time and do this create view with the same name on the same database? Or, is it like a SQL cursor where it is not related?
>
>What I finally did is to define a view creation program that I will run manually. Then, from a form, I only add the view in the DE. If I ever want to update my view, I will change my program and run it manually. Is that a good way to go?
>
>BTW, it is funny do that manually. I have a bunch of relations in the program but when I look in the DBC, they're not shown. However, it is running great. :)

Michel,

You found the solution by yourself. Running the program only once (per .DBC) minimizes the risks compared to defining the vue in the load() method of the form.

I don't know if your app has to be distributed or not. But if it has to be distributed, be sure the customer .DBC contains the view definition.

José