>I installed my vfp6 app on an NT server, and ran it like a WS, with the data on the same server. Crashes very quickly with ISOs, Cannot Update Cursor, Error Reading File, etc. Same problem as NTWS has.
>
>All runs fine on Win9x, any version.
>
>Also while debugging on the NTWS, I found that when I hit an error like ISO, and checked the data session window, all table aliases were still there. But when I clicked to open the one with a debugger line error (random different ones), it Browsed as an empty table, and vfp6 shutdown completely a second later each time, obviously unhappy about it.
>
>It's losing the connection between the alias and the underlying table file under NT, apparently. "Why" is the question...

Some areas I'd look into:

1. Security - were you logged in as a local or domain admin when you ran your VFP6 app? Are there any unusual or non-vanilla security policies in place (e.g. limiting disk space usage, inability to write/update temporary files, etc.)? Although come to think of it, limiting disk space is Novell-only, I think. But it sure would be a subtle bug if it was in place, eh?

2. Is there anything non-vanilla about the server hardware? Or, is there anything in *common* with other NT boxes that have been having problems - like the same make/model of NIC, etc.?

3. Have any tweaks been done to NT to support other apps? I had a client running a ported-from-Unix accounting app on NT, which required that "opportunistic locking" be disabled on NT (which is enabled, by default).

4. Is the NT server running any real-time virus scanning software? If so, can it be disabled for testing?