>George,
>
>Actaully, I am using Codebook. And, for each application you have a path that is set, first to the local directories for the ap, and then to the common framework library directories. This path allows you to run the ap without building it. A real time saver, believe me!
>
>This is set by a program called startcb.prg. Each ap has its own startcb.prg...
>
>The same path/program that works in 5.0 gets cut off at about 200 characters in 6.0.
>
>So, it is not what or how I am doing, since I am doing it the same in both versions... I beleive it is a 6.0 issue/problem.
>
>BOb
>
>PS: Where do I report bugs for VFP 6.0 ???

Bob,

I don't think that there's a bug here. I successfully set my path (using a COMMAND = statement in CONFIG.FPW) to well over 600 characters. The path statement included a long directory file name with spaces.

A couple of things come to mind, none of which, however, I've checked out. So forewarned is forearmed. 6.0 deals a lot better with long file names than 5.0, so if there are any directories that were entered as short names, I'd try replacing. Second, do all the directories exist, and are you sure that there isn't a typo? That might cause it to truncate it. The following might be helpful. Take the path you're trying to assign and assign it to the variable lcpath, then run the following, making sure foxtools is available:

* lcpath is the path to check
LOCAL lni, lnwords, lni, llhere, lcdir
SET LIBRARY TO FOXTOOLS
lnwords = Words(lcpath, ";")
lni = 0
llhere = .T.
DO WHILE lni < lnwords AND llhere
  lni = lni + 1
  lcdir = WordNum(lcpath, lni, ";")
  llhere = DIRECTORY(lcdir)
ENDDO
IF NOT llhere
  ? lcdir
  ? lni
ELSE
  ? "All directories exsist"
ENDIF

hth,