>Hi Fred
>
>Yeah thats a possible Fred. I considered doing it but shyed clear because I had not used the technique with views before only with tables and I had assumed that I would have had to force a disk presence for my view. Thinking about it though I guesss it is as simple as USE AGAIN myviewname.
>
>It should be pretty effective.
>
>I could establish the used again view(2) when I first establish my first view(1) so not much overhead.
>
>I take it that the view(2) will always be a complete clone of view(1).
>By that I mean whatever changes I make to records in view(1) will always be imediately impacted on view(2).

Caution here. View(2) may NOT be an exact clone of view(1) as it may contain more up-to-date data than view(1). Really depends on how often the backend data is being updated.

>I could even create a class that creates View(2) and also contains the properties and methods for doing a range of standard totalling/calculating functions on a view.

Very useful idea.

>Unless you see anything wrong with the above I will do it that way next time.
>
>Thanks
>

See above caution.