Subject goes hereRe: When open doesn't

2002-05-24 Thread notthatbbennett
[EMAIL PROTECTED] wrote: As a detour, have you tried opening a pipe from type to allow you to read the file contents via perl? No, haven't, but I think it would probably work, and its a pretty good idea. What I'll probably do is Win32::File::FileCopy it back to a temp directory though (all I

Re: When open doesn't

2002-05-23 Thread notthatbbennett
Johan Lindstrom [EMAIL PROTECTED] wrote: When open doesn't, print the error message. Actually, I did. Its just that the system its failing on doesn't have a good internet connection, and when I was describing the problem, I was typing in stuff from memory and I forgot to enter the code

Re: When open doesn't

2002-05-23 Thread notthatbbennett
[EMAIL PROTECTED] wrote: Change your argument to: E:/BU_0/C/Prefs The backslash is escaping the characters it preceeds. Alternative: E:\\BU_0\\C\\Prefs Nope. Already done both of those (and a lot of other permutations). I may be a UNIX guy, but I've been in double-backslash hell enough to

Re: When open doesn't

2002-05-23 Thread notthatbbennett
[EMAIL PROTECTED] wrote: Are you trying to open a file or a directory? If a directory, you will need a trailing slash. If a file, you will almost certainly need to specify a file extension. What is your E drive, attached or networked? If networked, have you tried the UNC name? Its a file, on

Re: When open doesn't

2002-05-23 Thread notthatbbennett
[EMAIL PROTECTED] wrote: This doesn't line up the output as it should but are the results what you expect? fairly lengthy program deleted Thanks, I'll give it try next time I'm near the system in question. It might turn up a clue or two. BB ___