John,

>I am just wondering that, how come this issue is niot handled but framework natively? Why don't MetaDBCMgr call SetDBCPath() to all databases recorded in metadbc.dbf once it automatically rather than called manually? Isn't it most application created using MM framework used fo multi-user environment, IOW, databases are not stored locally?

You're right...most developers using MM .NET are accessing their data on network drives rather than a local \Data directory.

Typically, you don't need to set a path to all the DBCs in your application because the CDatabaseManagerMetaData class handles all of this for you. Are you using this class as your database manager? You can specify that the MetaData Database Manager is used by setting your application's lUseDBCMgrMetaData property to true as described in the MM VFP Dev Guide topic "Specifying Additional Database Containers".

If this property is already set to true, I'm not sure what's going on here...you may want to try adding a call to SetPathToAppData in your application object's PreInitHook() method.

Regards,