Why am I getting an error here?

[Bruce Easton]

Kenneth Brody wrote Thursday, January 24, 2008 3:24 PM:
> Quoting GCC Consulting (Thu, 24 Jan 2008 14:46:26 -0500):
>
> >> -----Original Message-----
> >> Of Walter Vaughan
> [...]
> >>
> >> Boaz Bezborodko wrote:
> >>
> >> >Here is the line:
> >> >
> >> >ac(100,*)="!PDF /f\\server\data\fpro\temp\"&flname{".pdf"
> >> >
> >> >
> >> Because you are escaping the quote after temp with the \, so you are
> >> getting three quotes instead of 4
> >
> > You can replace the windows \ (backslash) with a normal slash /.
> >
> > ac(100,*)="!PDF /f\\server/data/fpro/temp/"&flname{".pdf"
> >
> > This will be read properly by the windows os.
>
> It depends on what he's going to do with that value.  While Windows and
> MS-DOS have always[*] accepted either slash at the kernel/API level, there
> are programs that require backslashes in pathnames passed to the in order
> for that program to parse the command line properly.
>
> For example, while my copy of "cat" happily accepts either slash, the
> command shell itself (either command.com or cmd.exe) will not allow me
> to use forward slashes for "type".
>
> However, if it requires backslashes, simply put a space between the
> backslash and close quote, and use "{" to squeeze it back out:
>
>      ac(100,*) = "!PDF /f\\server\data\fpro\temp\ " { flname { ".pdf"
[..]
> KenBrody at BestWeb dot net

Good to know - that's a lot simpler than what I wound up doing recently
when I needed to express similarly - and I think it went something like:

Then: bs=chr("92")
  If:
Then: path1=bs{bs{rootpath{bs{somepath{bs{somefl

Of course that just a lot more bs than is needed based on your example.

Bruce

Bruce Easton
STN, Inc.