Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
"Your network access was interrupted...
398 views
Skip to first unread message
BobAlston
Feb 17, 2012, 11:12:12 AM2/17/12
to
Anyone know the SOLUTION to this error message?
Database is a single MDB located on a workstation PC which functions as
a server. This can occur under Access 2003 or 2007.
bob
Database is a single MDB located on a workstation PC which functions as
a server. This can occur under Access 2003 or 2007.
bob
Bob Barrows
Feb 17, 2012, 12:31:41 PM2/17/12
to
"BobAlston" <bobal...@yahoo.com> wrote in message
news:jhlu8k$5uq$1...@dont-email.me...
PW
Feb 17, 2012, 3:40:08 PM2/17/12
to
issues, sometimes related to nearby fax machines, etc.. too close to
the PC that the data was on.
I know little about networks!
-pw
Access Developer
Feb 17, 2012, 4:37:15 PM2/17/12
to
As Bob Barrows said, "Fix the network."
Using Access/Jet/Ace as a split database in file-server mode, it is very
sensitive to a dropped connection, even one brief enough to not be obvious,
or one quickly self-repaired that doesn't interfere with other applications.
If a wireless network, wire it up... wireless networks are highly subject to
intermittent, often-unexplained, temporary interruptions. If a wired
network, check the Network Interconnect Cards (NIC) and replace the bad
ones. If neither works, contact the most knowledgeable of your network
support staff.
I have known, in the past, of a few organizations which solved similar
problems by complete replacement of the network support staff. <BIG GRIN>
You can be limited in the number of concurrent connections available on
"just another PC" (a network peer / client) used to contain the data store
part of a split database; if that's the problem, put it on a domain server
and have the clients log in to the domain. (Now this is where you want a
competent network staff... )
--
Larry Linson
Microsoft Office Access MVP
Co-Author, Microsoft Access Small Business Solutions, Wiley 2010
Using Access/Jet/Ace as a split database in file-server mode, it is very
sensitive to a dropped connection, even one brief enough to not be obvious,
or one quickly self-repaired that doesn't interfere with other applications.
If a wireless network, wire it up... wireless networks are highly subject to
intermittent, often-unexplained, temporary interruptions. If a wired
network, check the Network Interconnect Cards (NIC) and replace the bad
ones. If neither works, contact the most knowledgeable of your network
support staff.
I have known, in the past, of a few organizations which solved similar
problems by complete replacement of the network support staff. <BIG GRIN>
You can be limited in the number of concurrent connections available on
"just another PC" (a network peer / client) used to contain the data store
part of a split database; if that's the problem, put it on a domain server
and have the clients log in to the domain. (Now this is where you want a
competent network staff... )
--
Larry Linson
Microsoft Office Access MVP
Co-Author, Microsoft Access Small Business Solutions, Wiley 2010
Gilgamesh
Feb 21, 2012, 5:13:58 PM2/21/12
to
On Feb 17, 1:37 pm, "Access Developer" <accde...@gmail.com> wrote:
> As Bob Barrows said, "Fix the network."
>
> Using Access/Jet/Ace as a split database in file-server mode, it is very
> sensitive to a dropped connection, even one brief enough to not be obvious,
> or one quickly self-repaired that doesn't interfere with other applications.
>
> If a wireless network, wire it up... wireless networks are highly subject to
> intermittent, often-unexplained, temporary interruptions. If a wired
> network, check the Network Interconnect Cards (NIC) and replace the bad
> ones. If neither works, contact the most knowledgeable of your network
> support staff.
>
> I have known, in the past, of a few organizations which solved similar
> problems by complete replacement of the network support staff. <BIG GRIN>
>
> You can be limited in the number of concurrent connections available on
> "just another PC" (a network peer / client) used to contain the data store
> part of a split database; if that's the problem, put it on a domain server
> and have the clients log in to the domain. (Now this is where you want a
> competent network staff... )
>
> --
> Larry Linson
> Microsoft Office Access MVP
> Co-Author, Microsoft Access Small Business Solutions, Wiley 2010
>
> "BobAlston" <bobalst...@yahoo.com> wrote in message
> As Bob Barrows said, "Fix the network."
>
> Using Access/Jet/Ace as a split database in file-server mode, it is very
> sensitive to a dropped connection, even one brief enough to not be obvious,
> or one quickly self-repaired that doesn't interfere with other applications.
>
> If a wireless network, wire it up... wireless networks are highly subject to
> intermittent, often-unexplained, temporary interruptions. If a wired
> network, check the Network Interconnect Cards (NIC) and replace the bad
> ones. If neither works, contact the most knowledgeable of your network
> support staff.
>
> I have known, in the past, of a few organizations which solved similar
> problems by complete replacement of the network support staff. <BIG GRIN>
>
> You can be limited in the number of concurrent connections available on
> "just another PC" (a network peer / client) used to contain the data store
> part of a split database; if that's the problem, put it on a domain server
> and have the clients log in to the domain. (Now this is where you want a
> competent network staff... )
>
> --
> Larry Linson
> Microsoft Office Access MVP
> Co-Author, Microsoft Access Small Business Solutions, Wiley 2010
>
>
> news:jhlu8k$5uq$1...@dont-email.me...
>
>
>
>
>
>
>
> > Anyone know the SOLUTION to this error message?
>
> > Database is a single MDB located on a workstation PC which functions as a
> > server. This can occur under Access 2003 or 2007.
>
> > bob
At my workplace we had a big problem with access databases, both .mdb
> news:jhlu8k$5uq$1...@dont-email.me...
>
>
>
>
>
>
>
> > Anyone know the SOLUTION to this error message?
>
> > Database is a single MDB located on a workstation PC which functions as a
> > server. This can occur under Access 2003 or 2007.
>
> > bob
and .accdb, hosted on a shared networked drive. Access was running on
clients' PCs, but the database file happened to be on a networked
drive (not a client-server setup, just file access to a shared
drive). The problems occurred if a PC workstation was left
unattended for a time. The solution was to change the power settings
on the PCs to NEVER go to sleep; stay on all the time. We never had
any data loss or corruption, just Access freezing or giving us dire
warnings that the database might be corrupt. The problem was mostly
psychological in that it was unnerving having to kill Access or ignore
its warnings about a need to recover the database. Forcing the PCs
to never sleep fixed the issue.
Mike
BobAlston
Feb 21, 2012, 7:11:29 PM2/21/12
to
getting the message "Your network access was interrupted..."?
bob
Gilgamesh
Mar 2, 2012, 7:36:05 PM3/2/12
to
No. At least not that I recall. I just thought it sounded like it
might have the same cause.
Plus apologies for the tardy response, my ISP or employer is blocking
emails from google groups, due to the amount of porn adverts, I
expect, so I do not get the email summaries any more.
Mike
0 new messages