on my works newtork i keep receiving the above message across multiple
databases. IT support havnt got a clue. the databases are all different and
there are no internal design problems. Is this a problem with the network,
the software itself or something different all together.

The probelm occurs when you try to save the records.

thanks.

definitively a network problem

Pieter

"MW" <(E-Mail Removed)> wrote in message
news:F699B531-D00A-42C8-98F9-(E-Mail Removed)...
>
> on my works newtork i keep receiving the above message across multiple
> databases. IT support havnt got a clue. the databases are all different
> and
> there are no internal design problems. Is this a problem with the network,
> the software itself or something different all together.
>
> The probelm occurs when you try to save the records.
>
> thanks.

On Fri, 26 Oct 2007 02:24:04 -0700, MW <(E-Mail Removed)>
wrote:

It's a problem with the network. This will include the client NIC, the
cables, the switches, the server NIC.
Access is very sensitive to momentary interruptions.

-Tom.


>
>on my works newtork i keep receiving the above message across multiple
>databases. IT support havnt got a clue. the databases are all different and
>there are no internal design problems. Is this a problem with the network,
>the software itself or something different all together.
>
>The probelm occurs when you try to save the records.
>
>thanks.

On Oct 26, 4:47 am, "Pieter Wijnen"
<it.isi.llegal.to.send.unsollicited.mail.wijnen.nospam.ple...@online.replace.with.norway>
wrote:
> definitively a network problem
>
> Pieter
>
> "MW" <M...@discussions.microsoft.com> wrote in message
>
> news:F699B531-D00A-42C8-98F9-(E-Mail Removed)...
>
>
>
>
>
> > on my works newtork i keep receiving the above message across multiple
> > databases. IT support havnt got a clue. the databases are all different
> > and
> > there are no internal design problems. Is this a problem with the network,
> > the software itself or something different all together.
>
> > The probelm occurs when you try to save the records.
>
> > thanks.- Hide quoted text -
>
> - Show quoted text -

Yes, definitely a network problem. We had certain users having this
problem. On a couple of them when we chnaged their computers out (in
one sense changeing out their NIC card) it resolved their problems. On
some other users that did not solve the problem but when we used their
same computer but put it on a different cable to the server, that
solved their problem.

Ron

MW <(E-Mail Removed)> wrote:

>on my works newtork i keep receiving the above message across multiple
>databases. IT support havnt got a clue. the databases are all different and
>there are no internal design problems. Is this a problem with the network,
>the software itself or something different all together.

Not the software. Every time I've personally seen Disk or network
error it's been because of an intermittently flaky connection. Almost
always the same with the newsgroups.

Like the other folks I would agree that this is almost certainly a
momentary intermittent lost connection somewhere on the network.

Does it happen on one or two or many workstations? If one or two work
then the problem is the PC network card, cable or switch.

Does the cable run over the ballast on fluorescent lights? It's not
supposed to.

If many workstations then it's the switch/hub or the server network
cable or the server network card.

For more causes, including welding machines, flaky overload power in
an old house, etc, etc. see

For more information on corruption including possible causes and
determining the offending PC, see the Microsoft Access Corruption FAQ
at http://www.granite.ab.ca/access/corruptmdbs.htm

Note that IT departments don't usually like being told their network
is bad. They'll do their best to blame Access and tell you that you
should go to a .Net solution utilizing SQL Server. Never mind that it
would take 3 or 5 times longer to come up with the same solution.

Tony
--
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]" <(E-Mail Removed)> wrote in
news:(E-Mail Removed):

> Every time I've personally seen Disk or network
> error it's been because of an intermittently flaky connection.

These can be caused by hardware or by software. I've seen several
cases of updated NIC drivers on workstations on a LAN eliminating
the problem. And the workstations involved were not the ones
experiencing the problem (i.e., PC1 was getting the error connecting
to SERVER whereas PC2 was having no problems; updating the drivers
on PC2 fixed the problem). I've also seen adding a new PC to a LAN
cause the problem until the NIC drivers were updated. Because of
that, I try to remember to check for updated network drivers
whenever installing a new PC. I don't always install them
immediately (if it ain't broke, don't fix it), but I do download it
to the PC involved (or to a server if there's more than one PC with
the same NIC) just in case it turns out to be needed.

But I'm also usually the sysadmin for my clients, and not just the
Access developer. But Access developers need to know these things in
order to prod the sysadmins into doing all the appropriate
troubleshooting.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/