General information
Category:
Databases,Tables, Views, Indexing and SQL syntax
>>One of the things that I have run up against is that a view is harder to maintain if you are changing or adding views once you ship a application....
>Why is it harder?
Well I have to get my hands on the table or write code to add the view in the field. OTOH, with a cursor I just change the code at the office only...
>When you have a new table you have to add that table to the dbc
>When you have a new view you have to add the view definition to the dbc.
>So far nothing difficult
Not really difficult but adds time to the app vs a cursor if you don't need a view
>The only thing is that if you have read-write views that you also have to set the properties of the view to do that.
>I agree that you need more code for a view but it is possible.
I was just looking for validation or experiance on the cursor vs the view. Is there a reason to do the extra coding to use a view when you don't need the extra features of a view over a cursor? I can create an updatable cursor too but it seems to me to be easier to go the view route when I need to update from a subset of data from tables....
>They also told me to look at eView (from the files section) for shipping views. You may also look at that one
I have eView it is nice :o)
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only