Could it be that you have a loop somewhere that's tying up the processor? In that case put a Sleep(0) in there or DO Events...
>Hey all,
>
>We have three main VFP apps that our staff uses: we will call them apps A, B, and C. When people have app A running and then try to open the main screen in app B, app B hangs for a minute or more before opening the screen (an operation that usually takes under 10 seconds). We know the stalling is directly dependent on app A being open because the moment we close app A, app B is no longer stalled and the screen comes up OK.
>
>So, with some more testing we discovered that basically any two VFP apps can hose each other up, depending on what screens are up in any given app. When some screens are up, both (even all three) apps can all run fine. But when certain screens are displayed (usually the most complex ones) in one app, operations in the other apps will stall and take several minutes to complete.
>
>We thought it was the network...but we pulled down applications locally and the same thing still happens when apps A and B are totally local. We thought it was Foxuser issues, but each app creates its own resource files in separate directories. We thought it was DLL conflict, but on the machines in question, there is only one version of the VFP 6.0 runtime (SP3 DLLs).
>
>One final issue: This is only happening on Windows 95 machines. All the developers use WIndows NT (4.0 SP6) and we can run two, three, or ten VFP apps at the same time without having slowdown in any of them.
>
>So, HELP! I am at my wits end as far as what could cause this. I plan on downloading some monitoring tools to the PCs that act up (like WinTop, maybe a DLL monitoring tool?) to try to daignose this further, but if anyone has seen anything like this (or has ideas for further analysis), please let me know! Your help is very much appreciated!!!
>
>JoeK