Have been researching this for some time now, and I'm hoping someone
out there can help me.

I have an Access 97 database with Front End and Back End setup on
Windows 2008 R2 with Terminal Services (please no comments on the fact
that I'm running an old program on a current OS). The FE and BE both
live on the same network drive T:\MyFE.mdb and I have full control of
the folder and contents. If I open the database using the unc path (\
\server\databases\MyFE.mdb), it opens without issue and performs
flawlessly. If, however, I open the database using a mapped drive to
the exact same location and file, I get "Microsoft Access can't find
the database file 'T:\MyFE.mdb.' Make sure you entered the correct
path and file name." error and the database doesn't open. Is there
something I can do to fix this behavior, or do I just live with only
accessing the mdb from an unc path? It seems to be some type of
permissions issue, because if I copy the database from the T drive
over to my Documents library, it also opens without issue. If at all
possible, I would prefer to NOT have my users using UNC paths or
copying the FE mdbs to their documents so I can easily deploy updates
to them.

Thanks in advance for any guidance you can give me,
Jana

To be honest, I think you're better off using UNCs than mapped drives, just
in case the user unmaps a drive.


Doug Steele, Microsoft Access MVP
http://www.AccessMVP.com/djsteele
Co-author: "Access Solutions", published by Wiley
(no e-mails, please!)


"Jana" wrote in message
news:17fd3b62-e4b0-4741-a429-fe4972e7f2b1 (AT) u28g2000prm (DOT) googlegroups.com...

Have been researching this for some time now, and I'm hoping someone
out there can help me.

I have an Access 97 database with Front End and Back End setup on
Windows 2008 R2 with Terminal Services (please no comments on the fact
that I'm running an old program on a current OS). The FE and BE both
live on the same network drive T:\MyFE.mdb and I have full control of
the folder and contents. If I open the database using the unc path (\
\server\databases\MyFE.mdb), it opens without issue and performs
flawlessly. If, however, I open the database using a mapped drive to
the exact same location and file, I get "Microsoft Access can't find
the database file 'T:\MyFE.mdb.' Make sure you entered the correct
path and file name." error and the database doesn't open. Is there
something I can do to fix this behavior, or do I just live with only
accessing the mdb from an unc path? It seems to be some type of
permissions issue, because if I copy the database from the T drive
over to my Documents library, it also opens without issue. If at all
possible, I would prefer to NOT have my users using UNC paths or
copying the FE mdbs to their documents so I can easily deploy updates
to them.

Thanks in advance for any guidance you can give me,
Jana

On another issue, I'd chastise you for executing the front-end from a client
machine, AND, especially for having multiple users concurrently logged in to
the same copy of the front-end -- both of which can increase chances for
corruption.

It is trivially simple to automate distribution or to force users to
download a new, updated copy of the front-end -- MVP Tony Toews sells an
auto-updater at http://www.granite.ab.ca/accsmstr.htm and I have an article
on assuring that users download vital updated copies of the front end at
http://tripod.accdevel.com. There is just no valid reason, except sometimes
'recalcitrant IT departments who won't allow it for no good reason', to
_not_ distribute the front-end to the users.

--
Larry Linson, Microsoft Office Access MVP
Co-author: "Microsoft Access Small Business Solutions", published by Wiley
Access newsgroup support is alive and well in USENET
comp.databases.ms-access


"Jana" <bauer.jana (AT) gmail (DOT) com> wrote

On Fri, 5 Aug 2011 16:42:03 -0500, "Access Developer"
<accdevel (AT) gmail (DOT) com> wrote:

For what it's worth, and in my opinion, Access 97 was a lot more
stable sharing the FE than Access 2000 and newer. I still wouldn't
do that mind you.

Actually http://autofeupdater.com/ as I've moved it onto it's own
site.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/

"Douglas J. Steele" <NOSPAM_djsteele (AT) NOSPAM_gmail (DOT) com> wrote in
news:j1hmvf$5n8$1 (AT) dont-email (DOT) me:

I certainly agree, but as part of that, the shares on the server
have to be set up logically -- if you're Access databases are buried
10 levels deep under a top-level share, you're going to have
performance problems. I always put my Access databases in a
top-level share.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/