If I set oApp.lUseDBCMgrMetaData=.T. does it get the path from the metadbc.dbf or from the cLocalPath/cRemotePath properties? Or is the metadbc table path the default with the cLocalPath/cRemotePath used as overrides...i.e. what is the relationship between them?

TIA!

>Another fix for this is to use the MetaDBC for data pathing (oApp.lUseDBCMgrMetaData = .T.). Then, if you move the data, simply repoint the cLocalPath/cRemotePath entries. We use it to keep track of multiple client DBC's and as I'm our (hopefully temporary... are you listening, Bill?) DBA, I've run into these messages with relative frequency. At first they are a bear to track, as it appears you know by now. After a while, you recognize them pretty quickly, especially when it only affects your data.
>---J