Back end is Compaq Pentium 200 with 1 gig of memory and 36 gig of disk. SQL Server 7.0.

Developed a system on an NT W/S using VFP 6.0, SP3. DBC contains a remote view to the above mentioned SQL Server box synchronous (so we can get all records BEFORE we begin processing). Final production will call for the app to run on the server. All testing on the NT W/S was done interactively from a command line by calling a prg. Before moving into production, I decided to make a trial run on the server. Started VFP on the server and ran the prg from the command line with a SET COVERAGE TO ... command so I could review the results of the run. Initial tests on the NT W/S took about 2 hours, and 10 hours after initiating the test on the server, I stopped the process.

The hold up on the server is in the USE MetaData!rvContacts statement. rvContacts contains 250,000 records and uses an ODBC source to connect to the SQL backend. Further testing revealed the following:

USE MetaData!rvContacts from the NT W/S (connected to the SQL Server via 10mbit backbone) takes 10 minutes to run. This is acceptable.

USE MetaData!rvContacts from the Server running SQL Server takes 88 minutes to run. This is NOT acceptable.

This makes NO sense at all. Talked to the SQL DBA and NT gurus here and everyone keeps scratching their head.

The process should run in a couple of hours (updating and appending data to the SQL database from a native VFP database). But with that much time just to open one of two tables, and assuming that a REQUERY() will take the same amount of time as a USE will, the whole process will take days to run. Any ideas?