Treat a VIEW just like you would a TABLE. There is no need to execute anything.
-------------------------------------------------- Stubbornness is a virtue -- if you are right. --Chuck Noll
--------------------------------------------------
Thanks for the reply. I use this particular view in a mapping application. The user hovers over a piece of property and the address is displayed. What I'm finding, however, is that unless I go in and manually open the view, the data isn't being updated. I have written a module that brings in taxation data from a different system, which when a user double clicks on a parcel, the associated data is displayed. The data in this table is automatically updated daily. The address view draws it's data from this table.
Michael Kohler
Like I said earlier, VIEWS are a "virtual table that represents the data in one or more tables in an alternative way." That means you will need to interact with them in the same way you do a TABLE. Meaning you will in fact have to query the VIEW to retrieve the data you wish to display in your application. VIEWS pull their data directly from the tables referenced when you request it, not at creation. Therefor, there is no need to "refresh" a view. An Indexed View is slightly different, but it doesn't sound like that is what is being used here.
-------------------------------------------------- Stubbornness is a virtue -- if you are right. --Chuck Noll
--------------------------------------------------
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.