>>>Is it the actual SET PATH command that can't handle it? Can you do something like
>>>
>>>SET PATH to blah\blah, blah\blah
>>>Set Path to &AllTrim(set('path'))) + ',' + moreblah\moreblah
>>>
>>>or something like that....don't think that I've got syntax correct there...but you get my idea....
>>>???????
>>
>>Victor,
>>
>>I think it's probably just the overall length of the string. The path statement is part of the environment, and, to hazard a SWAG, probably has some limitations set on it. In this case, 1K.
>
>
>I am having some problems with a PATH statement, and searched and found this thread. While VFP seems to accept a path statement longer than 255 but shorter than 1024, it doesn't seem to actually work with a statement longer than 255. IOW, the additional paths are in there, but they don't get searched. Can anybody confirm this?

Mine runs 385 without problems. However, it is set in the registry, not in the design mode. That might be the problem. I'm wondering if you could write to the registry key, use the SYS(3056) function to re-read the registry.