CCL,

I sent the following message to Bill Wehrenberg via private e-mail. In case he hasn't told you yet...

Here is all you need to do to fix the hard-coded path problem:

1. In Cdbk30\ProjMgr\StartCB.prg change the path to point to the drive/directory where you have copied the framework files (I think you have already done this step). You can make the path relative by referencing "..\Common30".

2. Delete Cdbk30\Common30\Progs\Setup.fxp

3. CD to your own application's root directory and enter "DO STARTCB" in the VFP Command Window

4. Run your application by entering "DO MAIN" in the VFP Command Window

When the sample Project Manager is the first CBMM app that is run after installing the framework, it ends up storing a hard coded relative path "..\Common30" to the framework files in Setup.fxp. Executing the above steps recompiles Setup.fxp with a fully qualified path to Common30.

>The other question is in classes.dbf, two fields(clibrary and cfilename) are all empty, what data should be stored there?

The other empty fields in classes.dbf are for class libraries that are located in files that are external to your application. Unless you are using external class libraries, you can leave these fields blank. You can check out the section "Specifying External Class Libraries" in the Developer's Guide for more info on the subject.

Regards,