>>>>In WWC VFP servers, I opened about 35 files which are opened when WWC VFP servers start. Those are files I need for mostly all transactions. So, I open them up at first and only close them if a specific situation occurs. So, for each transaction, I don't have to open them up again. This is a time saver as I did the test by reopening them at each transaction and the time it takes is time I can't afford.
>>>>
>>>>My question is to know if there is an effect on VFP if I open more. Is 35 that much or I can open up to 50 without any problem?
>>>
>>>I have a WWC app that opens around 80 tables on the first hit, and they stay open after that. I haven't seen any problems stemming from this.
>>
>>Now, that's interesting. You mentions that they will be opened on the first hit. What kind of logic do you apply for that? Because, basically, you want them open for all instances of your WWC VFP servers. So, the first hit will hit only one server. What about the other 3? Also, what detection mecanism are you using to detect the first hit?
>
>Well, each server is responsible for itself, so the first hit counts for only one server. I simply check to see if one of the main tables is open, and if not, call the OpenTables method that first checks and then opens each of the other tables. I do it like this, because I have implemented a 'Maintenance mode' that returns all requests with a 'wait a minute' message. My admin page has a link to a method that closes all tables and puts a flag file in place. All subsequent hits check for that file before calling Opentables, and if it's there return before processing the hit. Once the flag file is deleted (another special hit), the next hit opens all the tables again. This is to facilitate table structure changes, reindexing, packing etc., and is all handled in my subclass of the Process class.

It's a good approach.