>We have a schema that uses two paired connections to the SQL Server backend. One handling transaction volume and one handling SQL Pass Through. The result is very nimble response.
>
Cool.
>SPT provides a level of versatility that the view designer doesn't. Note, the weakness is in the designer, not SQL. (ex. A situation where you want to retrieve data into a view that may come from any one of several tables that are structurally identical.)
>
Sure.. but the question wasn't, "What is better, hand coding SQL or using the view designer?".
Remember, you can hand code the SQL in the views too! The best advantage over views is that they are stored EXTERNAL to the source code, so it is possible to change the view without rebuilding your EXE.
BOb
Previous
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