Maybe the environment is too large and FB is calculating something that's wrapping around to a negative number. Did you try setting the initial environment to a smaller number like 256 or 512?

Just a thought,

>>Hi,
>>
>>Thanks. But I must be doing something.
>>
>>I set files to 99. DOS is high, UMB. In the shortcut I put EMS to 64. And in the Compatibility box I set Windows 95 (although Foxbase+ works with Me).
>>
>>I still get the same error message.
>>
>>In the shortcut I have the following settings: conventional memory: automatic
>>Environment at startup: 4096
>>Protected: not checked
>>EMS: 64
>>XMS: Automatic Using HMA
>>Memory for MS-DOS Protected Mode (DPMI): Automatic
>>
>>
>>As to the printer problem (which is quite unrelated to the memory problem) I think the problem is the today's computers are to fast for the SET TO PRINTER command to be used to write to files. But I have not yet found how to rewrite the code (eventually I will have to do that). My printer is a normal color laser hooked up through the parallel port and working fine.
>
>Hmm... the only thing I might suggest would be to turn off XMS and DPMI memory entirely if that is possible, for that shortcut. You could also experiment with compatibility with other versions of Windows.
>
>In the long run it might be better to simply recompile your app in a newer version of FoxPro/Visual FoxPro.