Can not open more than one database on a shared folder

[ChiefScott]

I have several databases in a shared folder on Server 2003. Users are all on
XP, with Officer 2003. If I have an Access database open (local or from the
shared folder) and try to open a second database (from the shared folder) I
get a path not found error. If I create a mapped drive to the share
everything works fine. I want to avoid creating a mapped drive on all users
workstations. Right now share and NTFS permisions are full control for
everone. Any ideas??

 

[Tom Wickerath]

I'm not sure what is causing your path not found error, however, any shared
Access applications *should* be split into two .mdb files: a front-end (FE)
file and a back-end (BE) file. Each user should have their own copy of the FE
file installed to their local hard drive. That way, your users should never
be attempting to open an application from the shared folder.

Here is an article that you should find helpful. The second paragraph
includes a link that discusses the benefits of splitting a database in
greater detail:

Implementing a Successful Multiuser Access/JET Application
http://www.access.qbuilt.com/html/multiuser_applications.html


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[ChiefScott]

Thanks Tom,

My data is in SQL 2005, with Access as the front end. I've been running
this way for several years, rather than making sure the most current front
end is on everyone's workstation, they hit the share. It was never an issue
until I stood up this new server with Server 2003. You can open up multiples
of everything except access from the share???

Lee.

 

[Tom Wickerath]

Hi Lee,

I don't understand this part of your comment:

....until I stood up this new server with Server 2003.

In any case, sharing an unsplit .mdb file, or the FE of a split application
amongst several users, has previously been identified by Microsoft as the
number one cause of JET database corruption. The recommended approach is that
each user is running their own copy of the application. I suppose you could
have several copies of the front-end on a file server, and in fact this is
the setup when using Terminal Server on a WAN, but for a standard server with
a LAN setup, this would only result in additional network traffic with no
benefit.

The classic argument against distributing a FE .mdb (or .mde) application to
each user is that it is difficult to distribute updates, whenever the FE file
needs to be changed. However, if you can use the free AutoFE Updater utility
that Access MVP Tony Toews makes available, then this upgrade process is
virtually painless. Here is a link for more information:

http://www.granite.ab.ca/access/autofe/details.htm


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[ChiefScott]

The share where the files sit is on a new server with Server 2003 R2 running
on it. The share used to be on a different server with Server 2003 on it and
I didn't have any issues. The old server was running SQL2000, the new one is
SQL2005. I'm almost 100% certain it doesn't have anything to do with SQL. I
can open up multiples of any other type of file. Access is the only files
giving me problems. Also there are sub-folders on the share and if you hit a
file in two different sub-folders the results are the same; the second file
comes up with the invalid path error.

I did find an obscure article about Enhance Internet Explorer Security on
Server 2003 R2 causing share problems, but turning that off didn't help.

I haven't had much trouble with databases going corupt on me, just throw a
backup on if it happens.

It's baffling to me that only Access is affected. I'll check out the AutoFE
Updater Utility, but I'd sure like to know why this is happening.

Thanks, Lee.

 

[Tom Wickerath]

Hi Lee,

but I'd sure like to know why this is happening.

I asked other Access MVP's if they had any idea as to what is causing this
problem. One replied back with the following response:

---> I would try to switch off "Use DDE" in folder options-file
types-mdb-edit-edit action "open"

If this works, please post back and let us know.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[David W. Fenton]

It's baffling to me that only Access is affected. I'll check out
the AutoFE Updater Utility, but I'd sure like to know why this is
happening.

What system db are you using? Is it in the same folder as the front
end or back end? Does it have a different name, not just extension?

(grasping at straws here)