For me probably the most important ones are:

* Easier error trapping

* More flexibility

* Slightly faster performance (much faster if you use Updateable views)

I have a wrapper class around my SQL Passthrough calls that can take
care of all of the connection management and error handling. It's much
easier that way to respond to errors immediately following a SQL
statement rather than letting an application handler take care of
this.

SQL Passthrough is more flexible, but it's also more work. Views
are picky if you change the database frequently and it's easy
to corrupt a database full of a lot of views, which is often
required to get all the queries you need.

As Bob pointed out SPT isn't much faster. Views are really just a fancy
parser for pre-created SQL syntax. There's some parsing overhead but
it's pretty small. The main thing to watch out for are updateable views
which can be really slow. When you work with SQL Passthrough you
typically don't use Updateable access (although you can) opting
rather to use straight SQL code to update the database.

+++ Rick ---