>An end user reports the following error message when an FOPEN() is issued: "class definition SCRIPTING.FILESYSTEM OBJECT is not found". Does anyone know what is missing here? I believe this is a WIN95 machine. TIA

This has nothing to do with the FOPEN(); it's reporting that Scriptng.FileSystemObject, a Windows Scripting Host component, is not properly installed on the machine, and it's actually erroring during a CREATEOBJ(). VFP does not natively reference the FSO. Win95 does not have WSH 2.0 or later installed unless steps were taken to install it, which would have included a requirement to update the DCOM and Shell Components in Win95, as well as the self-installing executable containing WSH or a very recent version of IE with tyhe optional WSH component selected.