Shane,
You might add a few Wait Window .... Nowait lines to the code. Put one at the very beginning of the main program, another just before the tables open, etc.

The wait window on the screen when the users get their slowdown will give you a clue - you'll know the problem is somewhere between that line and the next Wait Window.

You can even add one for each table loaded, the splash screen, etc. to narrow the results further. (Don't forget the "Wait Clear" at the end of the Init() so the users don't have the last one staring at them.

HTH
Barbara

>Barbara,
>
>The only tables being opened are the user (<24 records) and setup (1 record). I just talked to one of our clients this morning. The problem occurred again last week. 6 or 8 users were in using the application without any problems. Two other users tried to run the application and had this hanging problem. They both did an end task. An hour later they tried again. They both had the same problem. They had one of the users that was successfully running the application exit. One of them was then able to run & login successfully. The other user that was trying was too busy to try again.
>
>Most days they have up to 12 or 14 users running the application without any problems. The client tells me that they have tried waiting for a long time (30 minutes?) and eventually it did display the login form. It does seem to be a network traffic issue. I think it is a good idea to add the wait window debug messages to confirm that it is the opening of the tables that causes the delay/hanging.
>
>I read a KB article about VFP apps hanging using Novell Netware Client. Have you ever experienced this problem?
>