Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Security / January 2008

Tip: Looking for answers? Try searching our database.

Multiple User Access to DB Not Working?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Aaron Slater, Navy Region Northwest - 19 Dec 2007 21:51 GMT
Greetings;

I work for a reasonably large government agency that floats about the water
in big grey boats. We just upgraded our computers to Windows XP and now are
having problems with our databases.

Currently, in this office, I am the creator of a document tracking database
created in Access 2003. It is hosted on a shared network located off-site.
Previously, under the reign of Windows 2000, The personnel within the office
were all able to access the database simultaneously without complications.

Now after the WinXP switchover, When one person has the database open,
nobody else can open it. They will double-click on the icon, and nothing
happens. Access will not attempt to load, and no error messages or dialogs of
any kind show up.

The one exception is myself. I can open the database at will regardless of
who is in it, but again, nobody else can open it at that time.

The steps I have taken are thus:

Under the file properties Security Tab, all users have full control of the
file.

In the DB, I have gone to Tools>Options>Advanced and under "Default Open
Mode" "Shared" is selected. This is the only advice out IT people could give.

Any help will be appreciated. Thanks!
Keith Wilby - 20 Dec 2007 08:58 GMT
> Greetings;
>
[quoted text clipped - 30 lines]
>
> Any help will be appreciated. Thanks!

The first thing I'd advise is splitting the db:

http://www.granite.ab.ca/access/splitapp/index.htm

Give each user their own copy of the FE.

There are also "features" you should turn off, such as Name AutoCorrect:

http://allenbrowne.com/bug-03.html

Keith.
www.keithwilby.com
Aaron Slater, Navy Region Northwest - 02 Jan 2008 17:12 GMT
Splitting the database isn't a viable option in our environment, and the name
auto-correct doesn't help. Are there any other suggestions I could try? Why
would this have worked before in Windows 2000, but not now in Windows XP?

> The first thing I'd advise is splitting the db:
>
[quoted text clipped - 8 lines]
> Keith.
> www.keithwilby.com 
Keith Wilby - 03 Jan 2008 09:04 GMT
> Splitting the database isn't a viable option in our environment,

Sorry, but I can't think of a single instance where splitting would not be
an option in a network environment.  If delivering the FE to your users is a
problem then you could have the application shortcut run a batch file to
copy the FE to the user's profile and then launch it.  It's a tried and
tested approach that works flawlessly for me.

> and the name
> auto-correct doesn't help.

Did you turn it off?  Did you address the other "features" of A2003?

> Are there any other suggestions I could try?

Not that I can think of.

> Why
> would this have worked before in Windows 2000, but not now in Windows XP?

The OS isn't the issue.  Having multiple users access the same file over a
network just isn't the way to do it.
Tony Toews [MVP] - 06 Jan 2008 03:54 GMT
Aaron Slater, Navy Region Northwest
<AaronSlaterNavyRegionNorthwest@discussions.microsoft.com> wrote:

>Splitting the database isn't a viable option in our environment,

Why not?  This is strongly, strongly urged by everyone within the
Access community.  And we can find the odd reference somewhere within
the Microsoft website.

I'd change employers.  Oh right, you're in the Navy.

Tony
Signature

Tony Toews, Microsoft Access MVP
  Please respond only in the newsgroups so that others can
read the entire thread of messages.
  Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
  Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

Tony Toews [MVP] - 06 Jan 2008 23:05 GMT
>>Splitting the database isn't a viable option in our environment,
>
>Why not?  This is strongly, strongly urged by everyone within the
>Access community.  And we can find the odd reference somewhere within
>the Microsoft website.

Or did we already have this discussion a few weeks ago?  I can't
recall.

Tony
Signature

Tony Toews, Microsoft Access MVP
  Please respond only in the newsgroups so that others can
read the entire thread of messages.
  Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
  Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.