Charlie, I use views built from tables most of the time. I would say, the process would depend on the size of the data in the table. If the tables are small, I would think that views on views would not be to slow. However, as the data grows, it will become slower in providing the results. I have found, that if you project to a temporary table and then create the second view, it runs a little faster.
I have built this process into command files and run the process each time so the data becomes refreshed and captures all the rows or changes made. Gary ----- Original Message ---- From: Charlie Parks <[EMAIL PROTECTED]> To: RBASE-L Mailing List <[email protected]> Sent: Saturday, April 26, 2008 1:22:02 PM Subject: [RBASE-L] - View based views In my database views built on other views seem to process much more slowly than views based on tables. Is there anyway to speed up the processing of view based views or is it better to use table based views? View based views have the benefit as new rows are inserted into table then they are automatically inserted into the selection where as wouldn't table based views need to have the table dropped and reprojected each time new data is added or a different selection is desired? These are views based on group by statements with counts so there may be two or more views nested\paired together before arriving at the view definition that I'm wanting to use. Is there a better way to do this? Spell a grand slam in this game where word skill meets World Series. Get in the game.
