Hi Hector, it seems to be a pos app, is not possible that it take so much time just inserting records in dbf tables. If your repository tables on the server have more than 1.5GB the problem is the size, remember VFP tables only allows up to 2GB. If this is the problem you must move some of the data to a historic table.
If the size is ok, you must check the indexes and if you have validations when inserting, if your program is performing too many validations while inserting, this can be another problem. To understand if the problem is one of the two previous, you can use some brand new tables and perform the process to watch if the problem is solved. If problem continues, the only remaining thing can be the network, but sending just less than 1000 records by terminal is not logical that generates delays. Are you using locks on the repository tables on the server? maybe the locks are not unlocking properly.
Let me know what you think.

John.



Servidor W10 ahora antes W7 era lo mismo.

Tablas libres VFP

Locales todo el día actualizan en el servidor a la noche.

Las operaciones son varias pero digamos que agregar un centenar de registros simples ya demora una eternidad aleatoriamente. Como detalle curioso cuando son concomitantes - varias terminales a la vez - el tiempo de demora es similar aunque los registros varían en cantidad significativamente.

I hope it is enough information.

Thanks

>There is no enough information to understand what is the problem. Please provide what are infraestructure of the app on the server, the network and if it's sql server or dbf tables.
>for example is not the same:
>1. client server with sql server using terminals w7 and w10 with the exe in the terminal
>2. client server with sql server using terminal server
>3. exe in a shared directory on the server sharing by network
>4. client server with dbs tables using terminals w7 and w10 with the exe in the terminal and dbfs in the server consuming a lot of bandwidth
>5. dbfs alone on each terminal and updating at the end of the day to the server.
>
>Knowing better your whole scenario will be easy to help.
>
>>Thanks, Dmitri. One of the servers had - and still has - disabled Windows Defender. I'll check anothers. Most of the time >process last up to 1 minute - anyway it is too long - but there are days it is up to 1 hour.
>
>>You think I should check terminals?
>
>>Noway. Fortunatelly my clients have patience...
>
>
>>I would check an Anti-Virus (disable it for testing). In my experience AV software always slows down the program.
>>HTH
>>
>>>Hi friends:
>>>
>>>A few month ago I started to have problems with my program when add records to tables.
>>>
>>>This happens at the end of the day when my system sends to server daily activity. There are up to 2 terminals and servers with W7 and W10 so I can't deduce is the OS.
>>>
>>>For example 97 records are added in 22 minutes a day when yesterday took seconds and tomorrow will take seconds again.
>>>
>>>Since there are 3 or 5 terminals is curious everyone take almost the same time when they do the process at the same time.
>>>
>>>I tried eliminate FLUSH but nothing changed.
>>>
>>>This doesn't happen in all, just a few clients. For the time it takes I think the problem is when try to lock record.
>>>
>>>Well. My clients solve the problem leaving machines turned on all night and as I started control the time I find sometimes all the process in take till 2 hours..
>>>
>>>Any ideas?
>>>
>>>Thank you.