Hi,

I am using CopyFile (Scripting.FileSystemObject) to copy file from one
location to another. The naming convention followed makes the file
names (+ the path) lenghty and the total characters can exceed 260
characters.

I would appreciate if you can let me know if there is any solution to
bypass max limit (Filename + Path) of 260 characters.

The copying of file from one location to another happens on the click
of a button in MS Access Forms.

Thanks in Advance.

Regards
Bala

Access Version : Access 2003

The files (can be any type of files like .xls, .doc, .pdf etc..) is
copied from local Computer to network drive.

"bala" <balkiir (AT) gmail (DOT) com> wrote

Well you can use short file names instead:

http://www.smccall.demon.co.uk/Strings.htm#ShortPath

On Oct 26, 10:42*pm, "Stuart McCall" <smcc... (AT) myunrealbox (DOT) com> wrote:
There lies the problem, the clients wants the naming convention to be
followed and the naming convention does creates long names. Any work
around?

Can't you get the short file name at runtime to pass to your CopyFile
procedure whilst keeping the full name stored/displayed?

Jon

"bala" <balkiir (AT) gmail (DOT) com> wrote

On Oct 26, 10:42 pm, "Stuart McCall" <smcc... (AT) myunrealbox (DOT) com> wrote:
There lies the problem, the clients wants the naming convention to be
followed and the naming convention does creates long names. Any work
around?

On Oct 27, 9:35*am, "Jon Lewis" <jon.le... (AT) cutthespambtinternet (DOT) com>
wrote:
That is a good suggestion but the client wants the files to be named
according to the naming convention (translated : long name). According
to them they want to identify the nature of the file by glancing at
the name.

What I also tried is using the short dummy name to copy file using
CopyFile and then tried to rename it with the long name but it didn't
work out.

I have search web and couldn't find any solution for it as Windows XP
as a max limit of 260 characters when NTFS file system can handle upto
32,000 char.

To be honest I think the bottom line is as per Stuart and your
suggestion the File Name (inclusive of the Path) have to be restricted
to less than 240 chars (to be on a safer side). A file name (including
Path) with lenght of 253 Chars also created problem.

If there is any work around well it would be nice if not have to start
the long never ending process of convincing the Client.

bala wrote:
Where are you copying the file to; network or C: drive?

What is so long; the filename or the folder name? If folder name, you
can map a drive letter
Set WshNetwork = CreateObject("WScript.Network")
WshNetwork.MapNetworkDrive "L:", "\\mydrive\share"

Then you'd copy the file to drive L:

If your filename is 250 chars+, wow!

On Oct 27, 4:25*pm, Salad <sa... (AT) oilandvinegar (DOT) com> wrote:
I am copying the file to network drive and yes it is 250 Chars +. That
is problem. Sometimes there maybe one subfolder or 2 at the max. The
name of the file (following the naming convention) tends to be
long.That is the killer here.

"bala" <balkiir (AT) gmail (DOT) com> wrote

On Oct 27, 4:25 pm, Salad <sa... (AT) oilandvinegar (DOT) com> wrote:
Well if your client insists on sticking with FAT32 file system then the only
(sensible) solution is to redesign the naming convention. They've
overstepped the mark, unfortunately.

On Oct 27, 5:18*pm, "Stuart McCall" <smcc... (AT) myunrealbox (DOT) com> wrote:
Sorry for the confusion, what the client as is NTFS File System even
then the limitation (Max Lenght of 260) comes into play because of
Windows XP.