In my case, it was the VFP Delete File that wasn't working, so, I used the Windows API DeleteFile and that worked fine, thus the idea. File() and Directory() are working for me in ActiveVFP vfp mtdlls. Examples:

IF ! DIRECTORY(oProp.AppStartPath+'temp')
	MD oProp.AppStartPath+'temp'
ENDIF
IF FILE(oProp.TempFile)
    DeleteFile(oProp.TempFile)
ENDIF

I assumed these also worked when run from within COM+...

>Thanx. It is good to know that I'm not crazy and someone else has had this happen to them also. What did you use to simulate File() and Directory()?
>
>Neil
>
>
>
>>Neil,
>>you may need to resort to using the comparitive Windows API command for some few VFP commands. They always seem to work...
>>>Hi
>>>
>>>I am using a vfp exe com server and a vfp mtdll com server for vfp-.net interop. I am experiencing differences between the 2 com servers in how they interact with the operating system, which is win 2k server.
>>>
>>>My asp.net application is using impersonation so that I can use vfp tables on different computers on my peer to peer network.
>>>
>>>The vfp exe com server has no problem issuing a command like:
>>>
>>> if Directory(“h:\Data\”)
>>> do something….
>>> Else
>>> Do something else…..
>>> endif
>>>However, the same exact command issued by the mtdll com server always returns .F. for if Directory(). I am able to get around the limitations by discontinuing the use of impersonation and falling back to an ASPNET user. I guess the impersonated user is missing the local security policy to read the directory info.
>>>
>>>Therfore: does anyone know what policy my impersonated user needs to be able to read directory info. Hopefully this will enable the mtdll version of if Directory() to work properly.
>>>
>>>Regards,
>>>Neil
>>>
>>>
>>>Impersonate user -- security settings for directory access Thread #904639 Message #904639