>
>Is there any other 'secret' I should know about Foxpro running under NT ?
>

Here are a few tips we found helpful in running Extended FoxPro apps under Windows NT. You can set these by right clicking on the application's icon and choosing Properties.

1. You can set FILES=### in Config.nt or build a FoxCfg.nt with any other system configuration details you want, then tell Windows NT to use that config file instead of the default. As I remember, you set it by clicking on the Windows NT button on the Program page.

2. Set DPMI memory to at least 4000K

3. Set NT's conventional memory to 630K.
There is a kind of conflict between Windows NT memory manager and FoxProX's memory manager that causes it to run standard FoxPro instead of extended. That was likely the cause of Larry Moody's problem described in thread#252536. Standard FoxPro has a limit of 25 workareas, so when his program failed at SELECT 30, it was because he was running standard FoxPro. The answer for us was to set NT's conventional memory to 630K. 640K defaults back to auto.
Here is our best guess as to what happens. Fox's memory manager checks the environment to see if enough memory is available for FoxProX. If not, it defaults to FoxPro. Windows NT Auto memory manager limits an applications memory at first, then expands to what ever the application requires. By then, though, Fox has decided there isn't enough memory available and has run FoxPro. By setting Windows NT conventional memory to 630, Fox sees enough memory, and loads the extended version of FoxPro.