>I ran across something a little wierd with the views in my project. I was wondering if someone would enlighten me with an explanation/discussion.
>
>In my original app I used remote views (and nothing but) for all of the forms in my project ( VFP 6.0 front end, SQLServer 7.0 back end). I ended up taking my project to a VFP consultant for suggestions/advice, and he wanted to know why I was strictly using remote views. In one of the VFP books that I had purchased upon starting this project (and trying to learn VFP) the authors were adamant about the use of remote views for accessing a DB other than FoxPro's native DB, saying they were just as fast, and easier to implement than anything else. Thus the topic of my discussion...
>
>I found that there is much less code involved when using views (as opposed to SQL pass through). I think they were correct about that. However, in a SQL table of 5 fields, containing 3500 records, loading the data (using a remote view in the DE) took long enough for me to count the records along with the counter on the bottom of the Fox Pro screen. (Maybe I'm exagerating a bit...) However, when I took the remote view out, and replaced it with a SQL select statement, the form loaded instantly.
>
>Am I missing something here? or do you really take a hit when using remote views?

My experience is that one of the biggest bottlenecks is the protocol that the ODBC driver is using. It is faster to use TCP/IP if your server is set up for it. Otherwise, you have to use Name pipes (if you still need Novell) or Multi-protocol which can be fast but then gets clogged up and drags.