>For over 6 months, I have been working with remote views to SQL without any problems. About 3 weeks ago, I began having problems with my application. Everything seemed to slow to a crawl. These are test databases and no additional data has been added to the databases in the last 6 months. A form which once loaded in less than 30 seconds can take 5 minutes just to load. I played with the Fetchsize and Share settings with no luck. I get a "Function Sequence Error" from ODBC if I try to share the connection or set Fetchsize to -1.
>
>According to the network/SQL administrator, no changes have been made to the network, ODBC or the SQL setup (I have to take his word on this). When I try to modify a view in the database (change the fetchsize, etc.), it takes the system over 5 minutes just to save the file. Sometimes, it seems to hang almost indefinitely. What would cause such slow database access? I tried every machine on the network with the same results. I am being blamed for this problem, but am clueless. An application that used to run, no longer runs. No changes were made to the data or application.
>
>Please help...
>
>Monique

This may be a long shot, but last year we had a similar situation at a client site. SQL Server 6.5 and VFP5 front end. Queries that used to take 30 seconds began taking 15-20 minutes!

The reason? One (or more) updates to MDAC (ODBC, et al) components contained a SQL Server driver that worked great with SQL 7, but absolutely DIED against SQL 6.5. The problem was on the client computers, not the server. Computers that got NT 4.0 Service Pack 4 got the bad driver.

Try to determine if ALL client computers perform the same, or if the problem is isolated to a subset of computers. If so, start looking for configuration changes, regardless of what they tell you <bg>.