Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Make directory
Message
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Miscellaneous
Thread ID:
00387484
Message ID:
00387514
Views:
13
>All:
>
>I had written a routine that creates dozens of subdirectories. It works fine on my computer but not on the clients computer. On the clients computer they get an API error and it crashes. A possible source of error is they had a FILES = 200 statement, with the spaces, which could mean that the files weren't reserved properly.
>

Removing both spaces on either side of the = is necessary to get it to work.

I use the internal MKDIR in VFP6 without trouble; some things to watch for:

(1) If you create directories off the root, you may run into the limit of the number of diectory entries in the root of the drive. Subdirectories are not subject to this knid of limitation.

(2) VFP native directory manipulation sometimes has problems if an intermediate directory has the System property set. Using the Scripting,FileSystemObject rather than the native VFP.FoxTools functions will get around this,

(3) If you are attempting to create a subfolder, the name of the subfolder must not conflict with a file name in that directory, IOW, if the file C:\MyDir\Temp exists, you cannot create a folder named C:\MyDir\Temp.

(4) Ensure that the user has create privileges in the intervening directories - this is especially an issue in WinNT/Win2K environments where not all users have rights to all local resources.

There's no need for the FoxTools functions; they're native in VFP5/6, and you can also use the Win32 API or Scripting.FileSystemObject to do thye same things.
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform