>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.
>

I do... put this statement in a program and run the program... then look at your path. Do it in 5.0, then in 6.0...

SET PATH TO data;libs;progs;include;graphics;metadata;menus;reports;T:\DEV\CDBK30\COMMON30\libs;T:\DEV\CDBK30\COMMON30\progs;T:\DEV\CDBK30\COMMON30\utils;T:\DEV\CDBK30\COMMON30\graphics;T:\DEV\CDBK30\COMMON30\include

(I have the above on all one line in the PRG wich is OK according to the docsI can have up to like 8500 characters on a command line.)

I also tried the above with commas instead of the semis-- and I aslo tried it as...

SET PATH TO data, ;
libs, ;
etc...

I no case does the path get properly set. According to doing a ? set('path').

BOb


PS: When you run set path to fox pro doesn't care if they exist or not until you try to use it.

Yes... I was able to set the path to 500 'X's...