>I am trying to call ArcView 3.2 from my VisFox (Version 7) app. using a RUN command with and without a '/n' . It isn't firing up and I suspect it's a memory problem. Can I limit the memory used by Fox on startup? Might there be other issues?

You'll want to create a .PIF SPECIFICALLY FOR ArcView to control memory allocation for the launched DOS VDM; I'm not familiar with ArcView, so I don't have specific recommendations for you. You can create a PIF by right-clicking the executable file and selecting the Properties menu point; you'll be presented with a multi-tabbed property sheet that will allow you to control many facets of execution, including the amount and type of memory provided, and the execution environment (environment variables, drivers, available open files and the like can be controlled via custom AUTOEXEC and CONFIG files under NT-family operating systems.) You can control the launch better using either API_APPRUN or the Wscript.Shell Run method, both of which will allow you to wait or not wait on completion to occur before continuing (API_APPRUN allows for asynchronous execution with polling for termination.)

The PIF is very desirable - if nothing else, it controls the CLose on Exit behavior of DOS VDMs independently of system-wide settings.