BOb,

>We were having some problems building the project, and we found that our path in startcb seems to be too long for FoxPro...
>
>We can only get about 200 characters in the path.
>
>I modified the program and pulled out the spaces and the 'reports' directory for now.
>
>Also, seems there is a problem using ; as screen continuation, at least we saw it. So, I modified the path to be all on one line with each directory seperated with semi's instead of commas.
>
>Is there a maximum length for the SET PATH TO ??

Yes...I *think* it's 256 characters...or thereabouts. Can you use the .. alias to reduce the size of your SET PATH statement?

>Also, in set up program, if you launch from main the path is set in the program... This path is different than the one in startcb... this requires me to run startcb after exiting the program. Shouldn't these paths match? Or, if startcb sets the path, why bother doing it again in the prg ?>

The path that is set at runtime in Setup.prg's SetPath is slightly different than the development path that is set in StartCB.prg (e.g. the runtime path includes directories such as OTHER, HELP and FORMS. We haven't changed this since the VFP3 days, and don't want to do it now to break backward compatibility.

That said, the Framework should be restoring your original PATH settings when exiting the application gracefully (translate: without crashing!)

In Setup.prg, the current SET('PATH') is stored in gcOldPath. When the CGlobalEnvironment object instantiates, the value stored in gcOldPath is stored in its cOldPath property. When you exit the application and the CGlobalEnvironment object is destroyed, if its lSaveOldSettings property is TRUE (the default), the original PATH is restored.

Regards,