>What is the "proper" directory structure for Codebook development? Is the project directory supposed to be at the same level as the \CDBK30 directory? I have a project that is mostly complete, but now I need to move it to another server. When I originally set it up, I put the CDBK30 directory at the root of the mapped drive on the server I was using. I then put the project directory on the same drive, but it is 2 levels deeper in the directory structure. The class libraries now have references to the mapped drive letters.
>(I didn't see anything in the MM Developers Guide indicating what the proper structure is.)

That's because there is no limitation on where you place your projects. They can be on any drive or directory...in fact, I never place my projects under Cdbk30. Instead, I place them directly under VFP. Here's my normal directory structure:

C:
\VFP
\CDBK30
\MyProject1
\MyProject2

However, as mentioned in the Developer's Guide you do encounter a problem when you try to move the project, due to VFP's hard-coded paths. However, I have a utility that is going to be released in the next version of the framework (later this month) that can move a Codebook project FROM any drive/directory TO any drive/directory. If your situation is critical I can send it to you sooner.

Regards,