James,

it has to work. There must be something wrong anywhere. It's just the question: What is it?

You could create a COM DLL based on a simple session class, give it a method Test() and put your USE command with the hard coded path in there. If it's working, then something in your original DLL is probably wrong. If it's not working then something with your component setup on the server must be wrong.

This could at least find out, where to continue the search.

Let me know, how things are going.

HTH,
Armin


>Armin,
>
>I set up a system dsn on my machine to access the foxpro data. It works fine. Why can't I just open the table? I have never had this problem before, and I can't imagine having to go through ODBC just to access my own VFP data through a com object.
>
>>James,
>>
>>I don't know what's going on inside your DLL, so just a suggestion: You could issue a
>>
>>

>>DIR (lcPath+"lotA.dbf") TO FILE c:\test.txt
>>

>>
>>or
>>
>>

>>DIR (lcPath+"*.*") TO FILE c:\test.txt
>>

>>
>>in place of the other code that fails and see what gets into the log file and if your DBF is listed there.
>>
>>HTH,
>>Armin
>>
>>>I have a COM object that I am instantiating remotely using the createobjex() syntax. It keeps throwing an ole error that the path to where my data is invalid, even though the path that it shows is correct!
>>>
>>>I am using a variable in my object to set my path:
>>>
>>>lcPath = "c:\Lot Assesment Reports\tables\"
>>>Use (lcTable + "lotA") in 0
>>>
>>>The ole error keeps saying that ""c:\Lot Assesment Reports\tables\lotA.dbf" can't be found, even if I can open the table from the command window on the other machine. I've been really banging my head against the wall on this one. The process is running remotely on the other machine (in COM+), so the path should be correct. Any help would be appreciated.