Intermittent "Disk or Network Error" message. Shutting down Access
and restarting mde at client resolves it.
Running fe.mde with be.mdb Access 2002. BE.mdb is on MS2003 server.
FE.mde's on each client's WinXP SP3 machine. BE.mdb is compacted
regularly, file size 20mb. FE is compacted before being distributed,
and is 11mb. There are anywhere from 20-40 simultaneous users, each
running their own FE.mde.

Message can even appear when the workstation is at rest (user went to
lunch and returns to find the message). There is an onTimer event
that checks for inactivity and exits the database if inactive for 4
hours. Other than that, can't think what it could even be checking at
the server if no one is at the machine.

Not everyone gets the error. It is intermittent, and someone might get
the message when all other users are fine.
Appreciate your input.

I would suspect network problems of some type.

A "bad" NIC card in the relevant computer(s) or a bad network component.

Is it always the same computers? If so, what do they have in common on the
network - same router, same set of ports, etc.?


John Spencer
Access MVP 2002-2005, 2007-2010
The Hilltop Institute
University of Maryland Baltimore County

On 3/24/2011 8:23 PM, Slickdock wrote:
> Intermittent "Disk or Network Error" message. Shutting down Access
> and restarting mde at client resolves it.
> Running fe.mde with be.mdb Access 2002. BE.mdb is on MS2003 server.
> FE.mde's on each client's WinXP SP3 machine. BE.mdb is compacted
> regularly, file size 20mb. FE is compacted before being distributed,
> and is 11mb. There are anywhere from 20-40 simultaneous users, each
> running their own FE.mde.
>
> Message can even appear when the workstation is at rest (user went to
> lunch and returns to find the message). There is an onTimer event
> that checks for inactivity and exits the database if inactive for 4
> hours. Other than that, can't think what it could even be checking at
> the server if no one is at the machine.
>
> Not everyone gets the error. It is intermittent, and someone might get
> the message when all other users are fine.
> Appreciate your input.
>

That was my first suspicion. But it does not seem to be the case.
These are computers with nothing in common across those network
components. When googling the error, I am surprisingly finding
software type replies. Like making sure the temp files are cleared
out, or checking the version of msjet40.dll. Since these are also not
factors, I thought I'd post my own discussion and see what else anyone
might be able to offer.

On Mar 25, 8:54*am, John Spencer <JSPEN...@Hilltop.umbc> wrote:
> I would suspect network problems of some type.
>
> A "bad" NIC card in the relevant computer(s) or a bad network component.
>
> Is it always the same computers? *If so, what do they have in common onthe
> network - same router, same set of ports, etc.?
>
> John Spencer
> Access MVP 2002-2005, 2007-2010
> The Hilltop Institute
> University of Maryland Baltimore County
>
> On 3/24/2011 8:23 PM, Slickdock wrote:
>
>
>
> > * Intermittent "Disk or Network Error" message. Shutting down Access
> > and restarting mde at client resolves it.
> > Running fe.mde with be.mdb Access 2002. BE.mdb is on MS2003 server.
> > FE.mde's on each client's WinXP SP3 machine. *BE.mdb is compacted
> > regularly, file size 20mb. FE is compacted before being distributed,
> > and is 11mb. *There are anywhere from 20-40 simultaneous users, each
> > running their own FE.mde.
>
> > Message can even appear when the workstation is at rest (user went to
> > lunch and returns to find the message). *There is an onTimer event
> > that checks for inactivity and exits the database if inactive for 4
> > hours. Other than that, can't think what it could even be checking at
> > the server if no one is at the machine.
>
> > Not everyone gets the error. It is intermittent, and someone might get
> > the message when all other users are fine.
> > Appreciate your input.- Hide quoted text -
>
> - Show quoted text -

On Fri, 25 Mar 2011 09:24:24 -0700 (PDT), Slickdock <(E-Mail Removed)>
wrote:

>That was my first suspicion. But it does not seem to be the case.
>These are computers with nothing in common across those network
>components. When googling the error, I am surprisingly finding
>software type replies. Like making sure the temp files are cleared
>out, or checking the version of msjet40.dll. Since these are also not
>factors, I thought I'd post my own discussion and see what else anyone
>might be able to offer.

This seems to be a "catchall" error message that Access sometimes issues when
there's a problem and the program cannot (correctly) identify the source of
the problem. I've had it happen a number of times, and in every case the root
of the problem was either a corrupt table record or a problem with the VBA
project. Correcting the error (which sometimes required deleting and
reentering a corrupt record, or rebuilding an index) solved the problem; in
none of the cases I've seen was there actually a hardware error.
--

John W. Vinson [MVP]
Microsoft's replacements for these newsgroups:
http://social.msdn.microsoft.com/For...-US/accessdev/
http://social.answers.microsoft.com/.../en-US/addbuz/
and see also http://www.utteraccess.com

Oh boy. A "Catchall" error message. I hate to hear that.
Thank you for your input...As for a bad record or table, the back end
is compacted nightly. I know compacting may not correct a "corrupt"
record, but often times the error appears when the user is not even
attempting to access a record...they are not even at the computer.
They see the message when they return from lunch or from an outside
meeting. As for a problem with the VBA project, the app is debugged
and compiled before distributing.

Any other thoughts, anyone?


On Mar 25, 10:17*am, John W. Vinson
<jvinson@STOP_SPAM.WysardOfInfo.com> wrote:
> On Fri, 25 Mar 2011 09:24:24 -0700 (PDT), Slickdock <slickd...@yahoo.com>
> wrote:
>
> >That was my first suspicion. But it does not seem to be the case.
> >These are computers with nothing in common across those network
> >components. *When googling the error, I am surprisingly finding
> >software type replies. Like making sure the temp files are cleared
> >out, or checking the version of msjet40.dll. Since these are also not
> >factors, I thought I'd post my own discussion and see what else anyone
> >might be able to offer.
>
> This seems to be a "catchall" error message that Access sometimes issues when
> there's a problem and the program cannot (correctly) identify the source of
> the problem. I've had it happen a number of times, and in every case the root
> of the problem was either a corrupt table record or a problem with the VBA
> project. Correcting the error (which sometimes required deleting and
> reentering a corrupt record, or rebuilding an index) solved the problem; in
> none of the cases I've seen was there actually a hardware error.
> --
>
> * * * * * * *John W. Vinson [MVP]
> *Microsoft's replacements for these newsgroups:
> *http://social.msdn.microsoft.com/For...-US/accessdev/
> *http://social.answers.microsoft.com/.../en-US/addbuz/
> *and see alsohttp://www.utteraccess.com

Open Control Panel and look under System and see if there is indeed disk
error ?


"Slickdock" <(E-Mail Removed)> wrote in message
news:e36fd781-f048-42da-8f31-(E-Mail Removed)...
Oh boy. A "Catchall" error message. I hate to hear that.
Thank you for your input...As for a bad record or table, the back end
is compacted nightly. I know compacting may not correct a "corrupt"
record, but often times the error appears when the user is not even
attempting to access a record...they are not even at the computer.
They see the message when they return from lunch or from an outside
meeting. As for a problem with the VBA project, the app is debugged
and compiled before distributing.

Any other thoughts, anyone?


On Mar 25, 10:17 am, John W. Vinson
<jvinson@STOP_SPAM.WysardOfInfo.com> wrote:
> On Fri, 25 Mar 2011 09:24:24 -0700 (PDT), Slickdock <slickd...@yahoo.com>
> wrote:
>
> >That was my first suspicion. But it does not seem to be the case.
> >These are computers with nothing in common across those network
> >components. When googling the error, I am surprisingly finding
> >software type replies. Like making sure the temp files are cleared
> >out, or checking the version of msjet40.dll. Since these are also not
> >factors, I thought I'd post my own discussion and see what else anyone
> >might be able to offer.
>
> This seems to be a "catchall" error message that Access sometimes issues
> when
> there's a problem and the program cannot (correctly) identify the source
> of
> the problem. I've had it happen a number of times, and in every case the
> root
> of the problem was either a corrupt table record or a problem with the VBA
> project. Correcting the error (which sometimes required deleting and
> reentering a corrupt record, or rebuilding an index) solved the problem;
> in
> none of the cases I've seen was there actually a hardware error.
> --
>
> John W. Vinson [MVP]
> Microsoft's replacements for these newsgroups:
> http://social.msdn.microsoft.com/For...-US/accessdev/
> http://social.answers.microsoft.com/.../en-US/addbuz/
> and see alsohttp://www.utteraccess.com

On Mar 25, 12:47*pm, "Phil Hunt" <a...@aaa.com> wrote:
> Open Control Panel and look under System and see if there is indeed disk
> error ?
>
> "Slickdock" <slickd...@yahoo.com> wrote in message
>
> news:e36fd781-f048-42da-8f31-(E-Mail Removed)...
> Oh boy. A "Catchall" error message. I hate to hear that.
> Thank you for your input...As for a bad record or table, the back end
> is compacted nightly. *I know compacting may not correct a "corrupt"
> record, but often times the error appears when the user is not even
> attempting to access a record...they are not even at the computer.
> They see the message when they return from lunch or from an outside
> meeting. *As for a problem with the VBA project, the app is debugged
> and compiled before distributing.
>
> Any other thoughts, anyone?
>
> On Mar 25, 10:17 am, John W. Vinson
>
>
>
> <jvinson@STOP_SPAM.WysardOfInfo.com> wrote:
> > On Fri, 25 Mar 2011 09:24:24 -0700 (PDT), Slickdock <slickd...@yahoo.com>
> > wrote:
>
> > >That was my first suspicion. But it does not seem to be the case.
> > >These are computers with nothing in common across those network
> > >components. When googling the error, I am surprisingly finding
> > >software type replies. Like making sure the temp files are cleared
> > >out, or checking the version of msjet40.dll. Since these are also not
> > >factors, I thought I'd post my own discussion and see what else anyone
> > >might be able to offer.
>
> > This seems to be a "catchall" error message that Access sometimes issues
> > when
> > there's a problem and the program cannot (correctly) identify the source
> > of
> > the problem. I've had it happen a number of times, and in every case the
> > root
> > of the problem was either a corrupt table record or a problem with the VBA
> > project. Correcting the error (which sometimes required deleting and
> > reentering a corrupt record, or rebuilding an index) solved the problem;
> > in
> > none of the cases I've seen was there actually a hardware error.
> > --
>
> > John W. Vinson [MVP]
> > Microsoft's replacements for these newsgroups:
> >http://social.msdn.microsoft.com/For...-US/accessdev/
> >http://social.answers.microsoft.com/.../en-US/addbuz/
> > and see alsohttp://www.utteraccess.com- Hide quoted text -
>
> - Show quoted text -

Is the disk error referring to the client or the server?

On Fri, 25 Mar 2011 11:12:42 -0700 (PDT), Slickdock <(E-Mail Removed)>
wrote:

>Oh boy. A "Catchall" error message. I hate to hear that.
>Thank you for your input...As for a bad record or table, the back end
>is compacted nightly. I know compacting may not correct a "corrupt"
>record, but often times the error appears when the user is not even
>attempting to access a record...they are not even at the computer.
>They see the message when they return from lunch or from an outside
>meeting. As for a problem with the VBA project, the app is debugged
>and compiled before distributing.

You're not connecting over a wireless link or a WAN are you? It might actually
BE a network error if so.
--

John W. Vinson [MVP]
Microsoft's replacements for these newsgroups:
http://social.msdn.microsoft.com/For...-US/accessdev/
http://social.answers.microsoft.com/.../en-US/addbuz/
and see also http://www.utteraccess.com

On Mar 25, 6:02*pm, John W. Vinson
<jvinson@STOP_SPAM.WysardOfInfo.com> wrote:
> On Fri, 25 Mar 2011 11:12:42 -0700 (PDT), Slickdock <slickd...@yahoo.com>
> wrote:
>
> >Oh boy. A "Catchall" error message. I hate to hear that.
> >Thank you for your input...As for a bad record or table, the back end
> >is compacted nightly. *I know compacting may not correct a "corrupt"
> >record, but often times the error appears when the user is not even
> >attempting to access a record...they are not even at the computer.
> >They see the message when they return from lunch or from an outside
> >meeting. *As for a problem with the VBA project, the app is debugged
> >and compiled before distributing.
>
> You're not connecting over a wireless link or a WAN are you? It might actually
> BE a network error if so.
> --
>
> * * * * * * *John W. Vinson [MVP]
> *Microsoft's replacements for these newsgroups:
> *http://social.msdn.microsoft.com/For...-US/accessdev/
> *http://social.answers.microsoft.com/.../en-US/addbuz/
> *and see alsohttp://www.utteraccess.com

No, standard hard wired LAN.

John Spencer <(E-Mail Removed)> wrote in
news:imidsl$ek7$(E-Mail Removed):

> I would suspect network problems of some type.

I disagree with this diagnosis. I have much more often seen this
error because of software or networking issues. The most recent was
a case where the server had NETBIOS over TCP/IP turned ON. We didn't
diagnose that as the cause until we moved the back end to a
different server that had it turned OFF.

A lot of domains get incorrectly configured for both DNS and for
domain name, the former because many people don't really understand
DNS, and the latter because many people don't get that an NT domain
is not the same as an Internet domain. You don't want to append the
domain suffix of your company's website, mycompany.com, to your
connection. Instead, you should have a domain name like
mydomain.local, which won't get mixed up with Internet domains.

I have seen both of those problems cause this kind of error. I've
also seen Exchange Server hotfixes screw up the SMB redirector on a
machine that was also a file server and lead to dropped network
connections and corruption.

All of those are software issues, and not hardware at all, unless
you define "hardware" as including "correctly installed and
configured drivers for hardware devices".

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/