PB can't compile with a UNC path

[J. Armstrong]

\\server1\mis\projects\update.bas

If the compiler is 16bit as Tom indicated (meaning that you are
limited to the old DOS path limitations) you are limited to two
directory branches or pathing statements:

So your first would be:

\\server1\mis - since the DOS path limitations can only see two
deep

Second one would be:

\projects\update.bas

State the first half in your code as is and then use the ChDir
statement in VB (if I read your post right) with the second half
of the path.

Should work... hope it helps

-John

------------------
-John
e-mail: [email protected]

[Knuth Konrad]

Originally posted by Scott Turchin:
Yes, that is why, and why your executables are 8.3 truncated as well

Yes, but you can change the resulting EXEs filename to whatever you like, without any problems.

Knuth

------------------
http://www.softAware.de

[Scott Turchin]

Yes, that is why, and why your executables are 8.3 truncated as well

We've learned to live with it, can't WAIT for the next release tho!

Just when I was going to give up writing code, it relaxes me and comes back to me...

And PS, want to thank everyone that helped me on my SPYDER project...It works BEAUTIFULLY...


------------------
Scott
mailto:[email protected][email protected]</A>

[Gregery D Engle]

Tom,

Thanks I don't suppose that is why my source file name is
always 8 characters too?

------------------
-Greg

[Tom Hanlin]

The PowerBASIC compilers for Windows are 16-bit programs that expect only 8.3 DOS-style filespecs. This does not apply to the code you write using PowerBASIC, which may safely use LFN and UNC filespecs within, say, an OPEN statement. I'll put it down as a feature request, however.

------------------
Tom Hanlin
PowerBASIC Staff

[Edwin Knoppert]

I have something similar with a substed drive within PBEdit.

I can not make use very well using a substed drive.

At the office i make use of a network device to store the includes.
At home i substed a dir.

??


------------------
[email protected]

[Gregery D Engle]

if I have a source that is here:

\\server1\mis\projects\update.bas

I ususally map that UNC to drive Z: and I add that file as a
resource in VB. so I simply double click on it and it loads.

Unfortunetly VB doesn't pass the drive mapping, instead it passes
the entire UNC path, and PB can't compile it for some reason.

If I open the file from the PBEditor and specify drive Z: it
works fine.



------------------
-Greg