I am an MS Access developer and I have been installing a front-end for an
Access application that I have written. On many of the win2k machines, users
have been getting a "Can't find database file (path name)" error message
when they attempt to start the local Access file. I know that their local
copy of Access is fine since they are able to open the same file when they
open it from a folder on our network. They only get the message when they
try to open the file from their own C drive. In every case, I have had to
give them local administrative rights for the application to start for them
(it works fine with local administrative rights). For obvious reasons, this
is less than ideal; especially now that more and more people are wanting the
application and more and more people are being upgraded to Win2k. I am under
the impression that they should be able to open any kind of file if they are
power users, which they are, but it doesn't seem to be the case.

Michael Kelty
City of Alexandria
Department of Mental Health, Mental Retardation and Substance Abuse Services

Hi Michael,

My name is Amy Vargo.  Thank you for using the Microsoft Access Newsgroups.

I have seen this issue before if the path to the file is over 127
characters.  On Windows 2000, the full path to the file cannot be over 127
characters, including the root.  

For example:  C:\My Documents\My File\Mydatabase.mdb.

If the path is greater than 127 characters, shorten the path.

I hope this helps!  If you have additional questions on this topic, please
respond back to this posting.

Regards,

Amy Vargo
Microsoft Access Engineer

This posting is provided 'AS IS' with no warranties, and confers no rights.
You assume all risk for your use. ? 2001 Microsoft Corporation. All rights
reserved.

I think your statement needs some claryfications.

If full path would be limited to 127 characters many Windows structures and
WinAPI calls would get scrued up when using the MAX_PATH constant.

--
Regards,
Lars-Eric
http://www.clippersweden.se