Microsoft KB Archive/110113

{| = BUG: Problems Running FoxPro for Mac on Read-Only Share =
 * width="100%"|

ID: Q110113

2.50b 3.00b MACINTOSH kbprg kbbuglist

The information in this article applies to:


 * Microsoft Visual FoxPro for Macintosh, version 3.0b
 * Microsoft FoxPro for Macintosh, version 2.5b

SYMPTOMS
If FoxPro for Macintosh is launched directly from a server that is locked for write access (a read-only share), the program will not terminate when you try to quit FoxPro (the QUIT command or the COMMAND+Q key combination will be ignored).

Furthermore, issuing a BROWSE command causes the "Not enough disk space" error message, and issuing a CREATE REPORT command causes the "Access denied" error message.

CAUSE
FoxPro for Macintosh is attempting to write to a read-only FOXUSER.DBF file.

RESOLUTION
To quit FoxPro in this situation, issue the following commands:

SET RESOURCE OFF QUIT If FoxPro for Macintosh is required to run from a read-only network share (for security reasons, for example), you must either point the FoxPro for Macintosh session to a read-write FOXUSER.DBF file or issue the SET RESOURCE OFF command. Each user running FoxPro from the network should launch FoxPro for Macintosh by double-clicking a CONFIG.FPM file. To save an individual's settings, add the following command to the CONFIG.FPM file:

RESOURCE = ":FOXUSER.DBF" Or, to keep FoxPro for Macintosh from writing to a resource file, add the following command to the CONFIG.FPM file: RESOURCE = OFF When either of these lines are added, FoxPro for Macintosh can be launched by double-clicking the CONFIG.FPM file. As long as the Macintosh is attached to the server, FoxPro for Macintosh will launch and use the settings in the CONFIG.FPM file.

STATUS
Microsoft has confirmed this to be a problem in FoxPro 2.5b for Macintosh. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.