The fact that you're seeing the problem on 4 different NT LANs is your most important clue. The problem is something they all have in common.

You say MS's own NT network runs your app fine... are you certain their conditions are similar to the test LANs you were using?

Regardless of whether your app runs OK on MS's LAN, does it contain anything that might be considered "unusual" (as I outlined in an earlier message)? This might give us a clue. I'm sorry if I seem a bit harsh picking on your app, but it's the most obvious thing all 4 NT LANs have in common (!)

OK, assume for the moment it's NOT your app...

1. Do the 4 LANs have any hardware in common? This could be PC make/model, networking equipment, etc.

2. Are the 4 LANs loading any 3rd party software in common, that might not be found in other NT LAN installations? You'll need to look at ALL software here, not just that which you think could make a difference.

3. Were all 4 of the test NT LANs set up BY THE SAME PERSON or COMPANY? If so, the installer could have consistently made the same setup error(s). If this is the case, find (yet) another NT LAN that was not set up by that installer.

I would counsel you to "keep grinding" on this. There's no magic here; networks are not maliciously "out to get you". There is something in common with the 4 networks that's causing the problem. Anything - ANYTHING - they have in common, isolate it or test with an alternative. "The truth is out there". (I guess that's a better sentiment than its alternate - "Trust no one") :-D

>Microsoft can run my app on their NT server and 98 workstations and they do not see the problem. If it was in the app, then it would not run fine under Novell and on MS's NT test LAN. My problem on 4 different NT LAN's, I do see the problem. I'm about as frustrated as you can get. Again, all help is really appreciated.
>
>John