>
I have spent the last week or so reading up on remote views and sql passthrough and came to the conclusion that spt is what Im going to use.
>

Good choice...


>
I read a discussion on Wiki about this. They argued that spt is better than rv because you can close connections after you done using them unlike rv wich stay open the whole time the view is open. (Better scalability)
>

As for scaleability and SPT, IMO, the big payoff is that you can access stored procedures. Also, using SPT does not lock you into the Fox-Box. If you needed to off-load code to something else, it is a lot easier to do when using SPT as opposed to RV's. Even if you don't want to use SP's, SPT allows you to use the full back-end language. i.e., you are not limited to those elements the RV designer understands...

Keeping connections open is a valid point. It is far better to have connections open only as long as you need them. Connections take up resources. And, the fewer simultaneous connections you have - the better.