>Hello @all!
>
>We are archiving Documents in a specific Subfolder Structure.
>now depending on Servername and UNC Path there can be very long path names...
>
>Two Questions
>1. The justxxx Functions are limited to 259 characters. If more, you get "Invalid file- or path name" Error.
>Any Ideas out there to solve this? (ok, i can make my own justxxx func with string ops, bud i want to know if there are other solutions/suggestions ;) )
>
>2. Are the any other functions that will fail?

Depending on exactly what you're trying to do, here are some ideas:

1. Enable long path support in Win10 and later: https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/ . You may need to do this on both workstation and remote server (assuming they both support it)

2. RoboCopy can support long path/file names: https://learn.microsoft.com/en-us/answers/questions/92676/how-to-overcome-long-file-path-issues-with-robocop.html

3. You could experiment with the SUBST command: https://wuhrr.wordpress.com/2011/01/20/use-subst-to-deal-with-long-path-names/ . There might be a Win32API call that does the same thing

4. Along the same lines, on the remote server you could create a share that is deep in the folder structure, then map a drive letter to it

I don't know which VFP functions will or will not work with long path/file names.