Fabio --

I shared parts of this thread with our network fellow who supports our customers. He had this to add.

Some of the things that you may want to check are these:
1. Is there a computer with a dying/bad NIC on it? This can cause chatter, and sometimes re-installing windows will seem to fix it till the next time. What happens is that the software on the NIC can get corrupted through overheating or the like, and the corrupted software corrupts Windows. This is a rare case of hardware causing software problems. Again rare but I have seen it on low grade NICS

2. Size of prog is larger and you are just overloading the server all at one point. Check the number of CRC's on your network. You may have to add an additional line to the server/increase HUB space.

HTH

Jay


>David,
>
>Thank you for the response.
>Today I have been on my customer's site in order to verify his problem more closely. I got some facts I would like to share with you all:
>
>- The slowness problem was sporadic. Sometimes the application simply halted without any visible or detectable motive.
>- There were no anti-virus software running on the server.
>- I have detected that some slow parts were related to points of the application where a number of DBF files were open; so I decided to verify these files...
>- I tried to USE all files that the application was trying to open and here I found a REALLY STRANGE situation...
>- Three tables of my aplication took minutes to be open (about 2/3 minutes through a USE [tablename] instruction). All three tables were very small and one of them had no records at all.
>- I did all these tests on the server in order to discard possible network latencies or issues.
>
>Now my doubt is: How can possibly a table with no records with a DBF of about 5 KB and a CDX even smaller can take so much time to be opened?
>
>Thanks!