>Ok All,
>
>I came accross this by accident. We were having problems with building our application at the office and determined it was becuase of the path. We could not get a path of more than about 200 characters in there.
>
>We tried going from commas to semi, since we were using semis for line seperators we thought that was causing a problem.
>
>Well, at home I was working on an ap, and looked at the path and it looked longer than 200... So, I did a length on the path and it was 586 characters.
>
>So, is this a bug in 6.0? We could not get a path set that was longer than 210 or so... but, in 5.0 I have a path of 586?
>
>Thanks,
>BOb

Hi Bob,

I don't think that there's any limitation in the number of characters. What may be happening, however, is a difference in the way VFP 6.0 retrieves the search path. Admittedly, I didn't take this up much over 200 (252 to be exact) characters. I think that if you use the Tools/Options/File Locations/Search Path to set the path, you'll be able to set it with as many characters as required.

I'm not sure of this, but I believe that VFP 6.0 uses the registry setting, and will override whatever CONFIG.FPW settings you make. Once you've got the path you desire, simply select the "Set As Default" in the dialog box.

If you have multiple versions of VFP/FPW (as I do) I use a short program to set some of this configuration information (inlcuding the path). I haven't found any limitation with this. The last line of the common CONFIG file is COMMAND=, and I use the VERSION() function to set the path depending on that.

hth,