Frequent disconects from network in Access 2007

[MrDeej]

Hello!

Recently we have been experiencing a problem with our accdb file.
We have a accdb wich is uses by some 10 computers all day. This is connected to a sql server.

We get an error message saying that network connection was lost and all functions in access stops working. The network seems fine on all other areas, so it is just the accdb which loses connection.

We have recently innstalled Office 2007 SP2, but i cannot confirm that the problem started just after we installed SP2.

In windows event log, on programs. We get an event which says "Officelifeboat heang, P1 msaccess.exe P2........"

I am open for all suggestion to what i can check.

[Megalog]

Are all your users running the same ACCDB file? If so, you need to distribute separate copies. Running the same front end file could be the problem.

[MrDeej]

All users use the same. This has never been the problem and i think it shouldnt be a problem because access is made for this type of operation. I also have posted this on Microsoft forum, without any answer..

Any more suggestions? If i have to distribute the .accdb at each clients computer i have a lot of job because it is almost 50 different computers wich occasionally uses this (about 10 at same time)

[missinglinq]

Sorry, but Megalog is quite correct here. This is just one of many problems created by multiple users sharing a single Access file. And you are incorrect; Access is not made for allowing multiple users to simultaneously use a single file!

The worst problem, and if you haven't experienced it yet, then you've just been lucky, is chronic corruption with repeated loss of data!

You really have to use split your database into a front end/back end configuration, and place a copy of the front end on each user's PC.

Linq ;0)>

[Megalog]

Access ISNT made for this type of operation. You seriously need to set up a distribution system. This can be something as simple as a batch file that people run which copies the latest client to their system and then executes it.

There's no software install involved, so it shouldnt be too hard to do this whichever route you take.

But, this isnt a guarantee to fix your network problem. It -is- a guarantee to cut down on potential database corruption (which you might already be having).

Access is the canary in the coalmine.. any network problems and it's going to drop dead.

[missinglinq]

Tony Toews has an excellent hack for automatically updating multiple front ends. I don't do things on this sort of scale, but people who do swear by the program:

http://autofeupdater.com/

Linq ;0)>

[Megalog]

Here's a dumbed down sample of what I use in a .bat file, if you need to get up and running quickly with this:

ECHO OFF
ECHO Updating Database, please wait...
DEL "C:\Data\Database.accde" /q

copy "O:\Network Path\Database Startup.lnk" "%userprofile%\Desktop" /V /Y
copy "O:\Network Path\Database.accde" C:\DATA /V /Y

START /MAX "C:\Program Files\Microsoft Office\OFFICE12\MSACCESS.EXE /runtime" "C:\Data\Database.accde"

This basically deletes any existing local copies, then copies the latest client along with a shortcut on the desktop. This shortcut points to the networked batch file, so this way everytime they execute it they're getting a new copy of the latest version.

[MrDeej]

We have been using Access with multiple users for 4 years now. On the most we hade 30-40 simultaniously users. We use .accdb front-end and SQL backend. During the last 4 years we never once have gotten "network connection lost", though we have been experiencsing other issues occasionally.

Either way, this have been going on for 3 weeks, and we now have to find a solution to the problem. I will contact our IT department and have them implement a batch file which runs on windows logon.

This does not solve the problem, it just makes it irrelevant.
We have just resently installed Office 2007 SP2, and i think the problem started after that, though i am not sure.

Thanks for the answers, i used the last one :=)