Network Interruption

[Nettie]

I am having a similar issue to https://www.accessforums.net/access/...tml#post167647. I have a front end and back end. The front end is on a different drive than the back end.

I have a form set up to enter data. When I try to enter new data, I get the same error: "your network connection was interrupted. To continue close and then open again." I am using XP. I have tried compacting and repair, restarting my computer, with no change.

[RuralGuy]

Are you on a wireless network? Access does not work well on a wireless network.

[Nettie]

No, I am not on a wireless network. When I restart Access, I am able to enter one thing in the form, and then I get the error again. When I restart my computer and get back into Access, the item I entered that looked like it was saved, is gone.

[RuralGuy]

I guess I could use some background. The BE is on another drive in the same computer? Has it *ever* worked correctly? Are you using ac2007 as it shows? Have you set your Trusted Location yet?

[Nettie]

I actually have two databases, both with a front end and a back end. The back ends are located on a network drive. The front ends are distributed to 14 people who store them on another drive. Each computer can access the network drive. Database A has been working fine and is a much larger database than Database B. Database B has worked in the past and works one day, but not the next, and works for one person but not for another, depending on the day. It doesn't matter which form I use in Database B. The problem still exists where I enter data in one field, save the record, go to another record and enter data, try to save that record but can't because I get the error listed in my previous post. I am using Access 2007 on Windows XP. I have set the trusted location on each computer so that it accepts content from the back end. It seems to be an intermittent problem that is getting worse. What I don't understand is why it happens on the smaller database and not on the larger one. One other thing, a table in Database A is linked to Database B. Could this be part of the problem?

[Rawb]

Are the users all storing the Front-end on their local computers? Or are the Front-ends being run from a network location as well?

Also, are all of your users running the same version of Windows/Access?

And finally (although this is a long-shot)... Is your network set up with hubs or switches? If you're using plain old hubs, then it could, theoretically, be caused by collisions on the network.

[Nettie]

Most of the users have laptops and store their front end on the local drive. There are a few with PCs who store the front end on a different network drive.

Yes, they are all running the same version of windows/Access.

I don't know how our network is set up. We are a large company and our IT department would have that information. If it is collisions on the network, why is it not happening on Database A?

[Rawb]

Well, that's one of the reasons that possibility is so low. I'd imagine that if it were an actual network issue, then it would effect both databases. It's possible that (assuming database A isn't used very much) it could simply be that you just haven't seen the issues with database A yet.

Are the back-ends stored on different drives? If so, then the drive database B's back-end is on might be going bad or the server could be having network issues (or just be overworked).

However, I'd say all that's pretty unlikely. It's more likely an issue with the database itself, although I couldn't tell you what exactly.

If the issue is only happening with users that have the Front-end stored on a network drive, then that's likely your issue. I always try to store Front-ends on local drives and use Mapped drive letters instead of UNC paths when linking to Back-ends.

If it happens with both "local" and "remote" Front-end users though, then it could be a weird Record locking or Transaction issue.

It's hard to be more helpful than that though because of how little info we have on the databases.

[Nettie]

Database A is actually used more often and is older than Database B.

The back ends are stored on the same drive.

It is happening whether the front end is stored on the network drive or the local drive.

There are also two other front ends that are tied to the same back end, so I have 3 front ends to 1 back end for both Database A and B. I will talk about Database B since it is the one having the problems, but both databases are identical in format. Database B is a list of clients we have that are associated with Insurance Company B. We have to authorize services for these clients to stay in their home, so one of the front ends is designated just for those authorizations. We also have to track when they transition into a hospital or nursing home, so another front end is designated just for transitions. The main front is where we keep track of demographics. When I start a new record (or try to change information in an existing record) for a specific client in that front end, it will let me save it, but if I try to enter a second one, an error will come up saying there is an internet interruption and I must close the database and reopen to continue. When I close it and reopen, the new record is still there, I try the process again to add the second record or change something else, and upon the second try, I get the same error. If I shut down my computer and reopen the database, that new record (or anything I changed before the error) is gone.

I wish there was someone here who could take a look at my databases and tell me if something is wrong with the way they are connected, but no one in our IT department has any expertise in Access.

Thanks for any insight you can give me!