Hi, all,

I have a VFP MTDLL which is referenced by an ASP.NET app.
The DLL is configured to open a database located on a different W2K Serever machine.
It is coded like this:

FUNCITON LoadData as Integer ;
  HelpString [Loads the VFP Database]
  lcDatabase = "\\W2KDOMAIN\DONW2K\DATA\"
  IF DIRECTORY(m.lcDatabase) ;
  THEN 
    OPEN DATABASE (m.lcDatabase+"mydb.dbc")
  ENDIF
  &&code omitted...
ENDFUNC && LoadData

This works perfectly fine the DLL is called from VFP command line and doesn't matter where the data is located (local or the server):

loObj = CreateObject("ClientAccess.CClientAccess")
loObj.LoadData() && Works 

The DLL is added as a COM reference to my ASP.NET project. I've created a wrapper class which helps other classes the web app to communicate with the VFP MTDLL object.

//Code omitted
public class CClientAccessWrapper
{
   private m_oVFPDB CClientAccess;
   public virtual void InitializeComponents()
   {
     this.m_oVFPDB = new CClientAccess();
     this.m_oVFPDB.LoadData();
   }//InitializeComponents
}//CClientAccessWrapper

An unhandled exception occurs when LoadData method is called, I found out that the DIRECTORY is returning .f. in the LoadData if and only if the path is pointed to the W2K Server. In other words, if the database is located on the local machine it works. It seems to be some sort of Security Policy/User Rights issue.

Can anybody point me into the right direction? I would greatly appreciate it.