[AccessD] Short vs. Long File Names - Does it matter?

No, it doesn't really matter, unless you are hard coding the path somewhere.
(ie, if you take the path, and store it in a table, and then try to use it
somewhere else.  If the system is saving the long file names, on one
machine, and you try to use that long file name on a system that wants the
short file names.....then there's a problem.  But if you just get the path,
and use it, on the same machine, it shouldn't matter.)
 
Drew

-----Original Message-----
From: Backroads Data [mailto:backroad at idir.net]
Sent: Wednesday, September 17, 2003 3:15 PM
To: AccessD
Subject: [AccessD] Short vs. Long File Names - Does it matter?


Hi -
 
When I use CurrentDB.Name in code, sometimes it returns using short names,
like this:
 
C:\DOCUME~1\JULIES~1\MYDOCU~1\DEVELO~1\SomeFile.mdb
 
and other times it uses long names, like this:
 
C:\DOCUMENTS AND SETTINGS\JULIE SCHWALM\MY
DOCUMENTS\DEVELOPMENT\SomeFile.mdb
 
Does anyone know why it would vary?  (Sometimes re-booting gets it to switch
back to long file names, but not always - and not today!)
 
I guess more important - does it matter?  In code I want to create a small
text file in the same directory where the app is stored.  Other code will go
look for this file and read its contents.
 
I'm using Access 97 and WinXP for development.  Finished product will be
Access97 runtime installed on anything from Win95 and up.  TIA for any
insights.
 
Best Regards,
 
Julie Schwalm
Backroads Data
www.backroadsdata.com <http://www.backroadsdata.com> 
785-594-6807

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030918/dda62463/attachment-0001.html>