At any rate, is there a solution here? There's also the possibility
that the drive may already be mapped to the system, in which case it
needs to know what the drive letter is and write to it.
Have you tried Buddy API? I've had situations where Buddy worked and
FileXtra didn't, on similar
No, this needs to be all done from inside Director without any
interaction from the end user. They can't even create the folder
path on the network drive because they say it is too much effort.
This network drive is a local drive to each store across the nation,
but it is managed from one
How would I use Buddy API in this case?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Kerry Thompson
Sent: Friday, August 03, 2001 6:39 PM
To: [EMAIL PROTECTED]
Subject: RE: lingo-l FileXtra 3 - can't create folder across network
in NT but can
At 16:23 03/08/2001, Steven Sacks wrote:
How would I use Buddy API in this case?
Hmm, I just confirmed the problem with FileXtra3 on my little network with
a UNC file path. The disheartening thing about it is that there's even an
example in the docs that uses a UNC path. Worse, it returns a 0
How would I use Buddy API in this case?
Buddy has a lot of the same file management functions as FileXtra. You can
check on the existence of folders and files, copy files, create folders,
and so on. I've found that Buddy works in cases where FileXtra fails,
especially on Windows. I'll admit
