>Thanks Dragan for joining discussion.
>
>Do you use this method in your applications ? To solve error 1709 ?

I didn't have the error 1709, but I use it all the same, for the ease of maintenance. Furthermore, while I was writing that, I thought views could best be served by creating temp DBCs for the life of the app, which can be killed after use. One for each user, and Open Data (ThisUser_ViewsOnly) alias UsualName. Hmmmm, does it support aliases? Well never mind, we may use it without aliases, provided the views have unique names.

>Erik Moore say that is not much better for response time and add more labor to maintain each workstation. What do you think about that ?

Yes, the workstation will get more load, but then there will be some less on the server. It's actually only three files (the DBC, its DCT and DCX), and it won't get too much read/writes (only when you open a view) so 1709 may be the primary reason if you decide to do that. However, if each user will have her own view_only DBC, then I don't see any obstacle to its being created on the local disk. You may do some benchmarking - and I don't expect any great difference.