PRB: Cannot Create Program Workspace

• Microsoft FoxPro for Windows, versions 2.5 and 2.5a
• Microsoft FoxPro for MS-DOS, versions 2.0, 2.5, and 2.5a

SYMPTOMS

You receive this error message:

   Cannot Create Program Workspace.

CAUSE

This error is generally caused by pointing the temporary files that FoxPro creates to an invalid directory, to a read-only directory, or to a drive that does not have adequate disk space to store the temporary files. These temporary files should be pointed to an existing workstation's directory (local, in the case of the LAN version of FoxPro) where the user has read/write privileges. The directory where temporary files are stored can be set through the CONFIG.FP or CONFIG.FPW file.

MORE INFORMATION

If the error occurs even though the temporary files have been directed as described above using ADDUSER.APP in FoxPro, the SET FOXPROCFG line in the AUTOEXEC.BAT file may not be getting executed during boot up. This line is inserted by ADDUSER.APP and points to the CONFIG.FP file. If it has been placed in the AUTOEXEC.BAT file after a command such as WIN (to start Windows), it will not execute. If FoxPro cannot find a CONFIG.FP or CONFIG.FPW file, it will point any temporary files to its default directory. If that default directory is marked read-only, the error will occur.

To determine if this is the problem:

1. Open CONFIG.FP or CONFIG.FPW and look for the following lines:

         editwork = <drive>:\<directory>
         sortwork = <drive>:\<directory>
         progwork = <drive>:\<directory>
         tmpfiles = <drive>:\<directory>
   

   Double-check that these temporary files are pointing to a valid directory and that the spelling of these lines is correct.

   If FoxPro is on a network, make sure that you have read/write privileges to <directory>. Point to a local drive if possible.

2. At the MS-DOS prompt, change to the directory in question to make sure that it exists. The CONFIG.FP file does not create directories.

3. Open the AUTOEXEC.BAT file. Check the placement of the following line. It should not follow the WIN command or any other command that starts a program.

         set foxprocfg=<drive>:\config.fp
   

REFERENCES

"Developer's Guide," version 2.5, Chapter 16, pages D19-2 to D19-5 "Developer's Guide," version 2.0, Chapter 18, pages D18-10 to D18-14