IMHO, to get more realistic C/S application, it would be necessary to rewrite some code, at least, to utilize back-end stored procedures.

>Sylvain,
>
>I have yet to (need to) do so, but isn't there just a bit more work and coding involved when moving to 'remote' data sources?
>You make it sound so very simple.
>
>Cheers,
>
>Jim N
>
>>One of the big advantages in using views, is that if you go with a database server in the future (SQL Server, Oracle, etc.), you will only need to change the views.
>>
>>The query builder is great for simple views, but it has it limits. You could run GENDBC, cut & paste the definition in code and go from there.
>>
>>>I've heard a lot of pros and cons about using views. This question is specifically related to one project that has 36 views. The views are killing performance. The complexity of some of the views makes it very difficult to make changes. The problem is that some of our views break in the query builder because of the complexity. Now we've got to maintain that code outside of the builder.
>>>
>>>I've used a lot of views and like the simplicity of the updatable parameterized views. I was curious if anyone had some approaches to the above problems that would ease some of the maintenance and performance headaches. Perhaps we've gone the wrong way and we should not even been using views.