thank you Sean, but I tried it with existing files.
the docs say, that if I provide the short name, I will get the short name.
since I get the short file name, whenever I baGetFilename(), the following shouldn't return void IMO:
It certainly looks like there's something "screwy" going on there. On Windows, baGetFilename() doesn't return the shortFileName but the longFileName - at least it does for me with XP.
This
-- "Dagobert:who ever allowed long fil#A34AD:with spaces should be#A34B0.txt"
is a very strange construction. Presumably #A34AD and #A34B0 should resolve to unique values within their respective directories. Odd that baLongFilename resolves properly but baShortFilename fails.
Even odder is that put baFileExists(longname) -- 0 fails, where baFileExists(filename) seems to work.
Did you try mailing Gary directly, or checking his forum (I'm not sure whether it's still active) for more help?
-Sean.
[To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
