Chdir & 5.6
Kenneth Brody
kenbrody at bestweb.net
Wed Nov 22 08:54:07 PST 2006
Quoting GCC Consulting (Wed, 22 Nov 2006 11:23:34 -0500):
> Not sure if this is the correct action for chdir or a bug
>
> I did the following
>
> If: 'drive letter"
> Then: xx=getenv("pfdata");sl=chr("92")
> If:
> Then xy=xx{sl{"foobar"
> If:
> Then: chdir xy
> If:
> Then: system batch.bat
>
> Starting on drive W:\gcc
>
> When batch.bat ran and I had it do a directory listing, it was in the
> root directory of xx not in xx\foobar.
>
> Now if is hard coded this
>
> If:
> Then: chdir "t:\foobar"
>
> And ran batch.bat, I was in the proper directory.
>
> Apparently chdir doesn't accept variables.
>
> Is the correct?
>
> I have worked out a solution to this problem for testing on my system
> and for actual use on a client's system.
If
chdir "t:\foobar"
works, but
chdir xy
does not, then all I can say is xy doesn't contain "t:\foobar".
Does xy happen to be defined with a length, and therefore has
trailing spaces?
Does
chdir xy { ""
work?
(As an aside, you don't need to use backslashes. Forward slashes
will work just as well.)
--
KenBrody at BestWeb dot net spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com
More information about the Filepro-list
mailing list