>>>Curtis,
>>>
>>>>Well, you make this sound like it's not indigenous to FoxWeb. So, I'm assuming that switching to WebConnection or another product will not fix this. This is a crying shame since VFP takes the longest opening files.
>>>
>>>I cannot comment on how FoxWeb does this, since I've never used it or seen it demonstrated.
>>>
>>>However, with Web Connection, you have one or more VFP EXE's running all the time on the server, waiting for requests to be handed off by IIS via wc.dll. You can let those servers keep files open, cached, and ready to fly, although you cannot count on anything like record pointers, which table is selected at the moment, etc. The point is just as you suggested -- the EXE's can keep the tables open for performance.
>>
>>Thanks, that's just the information that I needed. Now I'll have to check with FoxWeb to see if that's possible. But from what Bret Hobbs says, it is not. I've got a message into their Tech Support so that should provide a definitive answer.
>
>FoxWeb technical support has been very good to us. So if there is a way they will know.

FoxWeb Tech Support says "FoxWeb's Close Tables setting (accessible in the FoxWeb Control Center)determines whether tables are closed after each hit. If this setting is disabled then FoxWeb does not close open tables." So that's good news.