John,

Are you getting a different error -- about the table -- now? The reason I ask is that before you mentioned receiving a "database does not exist error" which means the database can't be located.

In our app, we have the need to open and close databases at runtime so we do that using the full UNC path (e.g. OPEN DATA '\\server\path\Client1.dbc'), but you can also use the database manager to add to the current path:

goApp.oDatabaseMgr.SetDBCPath('path to your dbc')

Hope that helps,
---J

>Hi,
>
>>>Is this happening everywhere or a few machines? If it's everywhere, make sure that the path is entered correctly in the MetaDBC. You can test by copying and pasting the entry from the MetaDBC into a FILE() command just to be sure there aren't any typos.
>
>I am use the path is correct because I locate the dbc using user preference. I also try to copy the path from window explorer and paste to metadbc.
>
>>>Can you tell which method is receiving this error? It sounds as if the environment finds the correct entry in your MetaDBC, yet can't find the physical .dbc file
>
>In
>Method: cDataEnvironment.OpenTables()
>
>THIS.oDataEnvironment.OpenTable().
>
>During debugging, I found that Cursor.OpenTable() doesn't open table, instead it just set property value since it set as AutoOpenTable = .T. and error occured while native dataenvironment.OpenTable() is called. Also, VFP is not reporting my view is not found, but the underlying table.
>
>Question: I didn't see MM framework set path to any folder I set in metadbc. How could VFP know where are my other databases?
>
>Thank you