I've trace the slowdown to the routine that opens and sets up the tables, cursors, local views, etc.

Thanks,
Arriyel

>Hi!
>
>Just a suggestion below...
>The problem not is the file downloading through the network itself, but in the way file is downloaded. Windows EXE file is not donloaded into the memory completely when running. Certain EXE modules are still on the disk and downloaded by application on the fly on-demand (for example, when user opens a form). This is specially for VFP EXE where major part of EXE file is ust a VFP interpreter internal code. When there are 10 users, and each try to open different forms, for example, the HDD heads require to jump a lot on the server machine to read different parts of that EXE file to serevr multiple users simultaneously. When there are only one user, there are no problems.
>
>Usually it is good idea to copy the EXE to each workstation.
>
>>Hi,
>>
>>We have a VFP6 application executable installed in a server with the data in a subdirectory. Users connect to the app by running a shortcut on their workstations. The executable is about 10Mb in size :) and so take quite a bit of time to load.
>>
>>The very first user to run the app connects fine (around 5 to 10 seconds) but all subsequent users (except one) takes over two minutes. We have one user running Windows ME on a Pentium III 900MHz and it can connect within 10 seconds no matter if it is the first or the last to login. All other systems we tested on was had Windows 98 SE on Pentium III 500MHz and faster except for one that had Windows ME also. All workstations have 128Mb of RAM with plenty of free hard drive space. The network is running on 100BaseT.
>>
>>Anyone know the cause or any solutions to this? Any help would be greatly appreciated. TIA.
>>
>>Arriyel
>>
>>P.S.
>>Connect in this case is getting to the login screen.