Michael,

Sounds like you might need to optimize the updating code a bit, if it takes more than 50 secs to update 50 records. Are any of the 50 records getting written?

Meanwhile, you can increase the timeout setting for Web Connect in the "wc.ini" file:

;*** Time to allow request to finish
;*** Process will be terminated after number of secs
;*** specified here.           REQUIRED 
Timeout=50

which defaults to 50 seconds.

However, you might want to post the code here that does the updating, in case someone can see a way to help you speed it up.

>I am running Windows 2000.
>I added another 64 megs for a total of 128 megs of RAM. The request is being processed by the server, (meaning you can see the request being executed by the server) but I am not receiving the proper result back from the query and the query still times out after 50 seconds. This happens mostly during the processing of a text file which contains 50 items with which to update the database. These requests are in a loop to process each request consecutively. (Therefore if 50 items are in this text file, 50 'update' requests are sent to the server, one after another). This problem is intermittent and doesn't occur at the same place in the application. It happens quite often. More so while executing the application in development using VFP than executing from an executable. Can you give me any more clues as to why this is happening? Thanks in advance.