>>>Firstly, you need to assess why you are doing this (there are some valid reasons, but this is not the normal way). Generally, it is enough to define a few parameterized views and just let them live happily and permanently in a server dbc. Parameterized views, if defined correctly, usually give enough flexibility to allow your app to run without creating any custom ones.
>
>Secondly, if you decide that temporary views IS the way to go, you need to be creating those in a temporary DBC on each users own hard drive, so you don't run into naming conflicts, etc.
>
>The reason to have is we are creating more than 50 views.


I suppose. I am having trouble visualizing a situation that would require this many views created dynamically, instead of several parameterized views, but if you are confident in the this design decision, then go for it.

>We are saving it in the server and using sys() function getting a unique name for dbc. Is that the right way?

I would personally make these temporary files reside on each workstation, but I guess local temp files is just a preference of mine.