Error Message: ErrorAccessing File. Network connection may have been lost.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I keep getting this error and not sure what it means. I am running access on a single pc that is not hooked to a network so It doesn't make sence. the problem is I can't build any forms because of this error. Can anyone help me?
 
Hi ,

My name is Michael Noto. Thank you for using the Microsoft Newsgroups. As
I understand, you are getting the message "Error accessing file. Network
connection may have been lost. "

This message indicates that the database has been damaged. This can occur
if there is a newer version of VBE6.dll (from a 2002 version product) on
the computer and is being used by Access 2000 which does not have the newer
service pack installed. The article below has steps to attempt to recover
the database objects that are damaged after you update office to the latest
service pack.


ACC2000: Error Message: Error Accessing File. Network Connection May Have
Been Lost.

http://support.microsoft.com/default.aspx?scid=kb;en-us;304548

I hope this helps! If you have additional questions on this topic, please
reply to this posting.

Regards,
Michael Noto
Microsoft IIS Support

This posting is provided 'AS IS' with no warranties, and confers no rights.

Please do not send email directly to this alias. This is our online account
name for newsgroup participation only.

Need quick answers to questions like these? The Microsoft Knowledge Base
provides a wealth of information that you can use to troubleshoot a problem
or answer a question! It's located at
http://support.microsoft.com/support/c.asp

From: "=?Utf-8?B?c3dpbHNvbg==?=" <[email protected]>
Subject: Error Message: ErrorAccessing File. Network connection may have
been lost.
Date: Fri, 2 Jan 2004 07:26:10 -0800
Newsgroups: microsoft.public.access.gettingstarted

I keep getting this error and not sure what it means. I am running access
on a single pc that is not hooked to a network so It doesn't make sence.
the problem is I can't build any forms because of this error. Can anyone
help me?
 
Take a look at this article and see if it addresses the issue you are
experiencing.

304548 ACC2000: Error Message: Error Accessing File. Network Connection May
http://support.microsoft.com/?id=304548

--
Kristyn Wagoner
Microsoft PSS

Please do not reply directly to this alias. This alias is for newsgroup
purposes only.

This posting is provided "AS IS" with no warranties, and confers no rights.
swilson said:
I keep getting this error and not sure what it means. I am running access
Click to expand...
on a single pc that is not hooked to a network so It doesn't make sence. the
problem is I can't build any forms because of this error. Can anyone help
me?
 
Michael Noto:
I have had this error occur, but I have Microsoft Office XP, not
Microsoft Office 2000. The Service Pack 3 only applies to Microsoft
Office 2000. Is there a fix for Microsoft Office XP?

Thanks,
Joy
 
Hi Joy,

I am sorry but I did not see your posting until now. That message indicates
a corruption of the database. The most common cause is the database was
opened in Access 2000 with the vbe6.dll file mentioned in the article but
corruption may be caused by other circumstances also.

I would suggest trying the steps in the article 304548 to recover as many
objects of the database as possible.

Another possible resource to recover datbase:
===========================================
How to Troubleshoot and Repair a Damaged Access 2002 or later Database

http://support.microsoft.com/default.aspx?scid=kb;EN-US;283849

I hope this helps! If you have additional questions on this topic, please
reply to this posting.

Regards,
Michael Noto
Microsoft IIS Support

This posting is provided 'AS IS' with no warranties, and confers no rights.

From: (e-mail address removed) (joydot)
Newsgroups: microsoft.public.access.gettingstarted
Subject: Re: Error Message: ErrorAccessing File. Network connection may
have been lost.
Date: 21 Jan 2004 07:22:21 -0800

Michael Noto:
I have had this error occur, but I have Microsoft Office XP, not
Microsoft Office 2000. The Service Pack 3 only applies to Microsoft
Office 2000. Is there a fix for Microsoft Office XP?

Thanks,
Joy

(e-mail address removed) ("Michael") wrote in message
 
Thanks Michael for the information.
Since Microsoft Office XP comes with the vbe6.dll file mentioned in
the article, is it recommended that all databases be upgraded to
Access 2002? We are currently supporting customers in various stages
of product life cycles so the database in question is always an Access
2000 one. This way it will work on systems having only Access 2000,
the least common denominator.
It would be nice if the upgraded vbe6.dll were tested under Microsoft
Office XP and a service pack released as a permanent solution.

Thanks,
Joy
 
Hi Joy,

The latest SP for office 2000 does prevent the corruption from occurring
when opening an version 2000 database using Access 2000 but applying the SP
will not repair the database. If the database is only opened using Access
2002 or 2003 then the corruption is not caused by the steps to reproduce
this error in the article below. Once the database is damaged, the
symptoms will occur in all versions of Access. The article has steps to
attempt recovering the forms, reports and modules of the database in the
resolution section. Objects wihout code such as tables are not damaged and
can be imported into a new database.

Here is the article again:

ACC2000: Error Message: Error Accessing File. Network Connection May Have
Been Lost.

http://support.microsoft.com/default.aspx?scid=kb;en-us;304548


I hope this helps! If you have additional questions on this topic, please
reply to this posting.

Regards,
Michael Noto
Microsoft IIS Support

This posting is provided 'AS IS' with no warranties, and confers no rights.
--------------------
| From: (e-mail address removed) (joydot)
| Newsgroups: microsoft.public.access.gettingstarted
| Subject: Re: Error Message: ErrorAccessing File. Network connection may
have been lost.
| Date: 29 Jan 2004 07:41:51 -0800
| Organization: http://groups.google.com
| Lines: 53
| Message-ID: <[email protected]>
| References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
| NNTP-Posting-Host: 137.100.73.40
| Content-Type: text/plain; charset=ISO-8859-1
| Content-Transfer-Encoding: 8bit
| X-Trace: posting.google.com 1075390912 9269 127.0.0.1 (29 Jan 2004
15:41:52 GMT)
| X-Complaints-To: (e-mail address removed)
| NNTP-Posting-Date: Thu, 29 Jan 2004 15:41:52 +0000 (UTC)
| Path:
cpmsftngxa07.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP08
..phx.gbl!newsfeed00.sul.t-online.de!t-online.de!newsfeed.gamma.ru!Gamma.RU!n
ews.maxwell.syr.edu!postnews1.google.com!not-for-mail
| Xref: cpmsftngxa07.phx.gbl microsoft.public.access.gettingstarted:144039
| X-Tomcat-NG: microsoft.public.access.gettingstarted
|
| Thanks Michael for the information.
| Since Microsoft Office XP comes with the vbe6.dll file mentioned in
| the article, is it recommended that all databases be upgraded to
| Access 2002? We are currently supporting customers in various stages
| of product life cycles so the database in question is always an Access
| 2000 one. This way it will work on systems having only Access 2000,
| the least common denominator.
| It would be nice if the upgraded vbe6.dll were tested under Microsoft
| Office XP and a service pack released as a permanent solution.
|
| Thanks,
| Joy
|
| (e-mail address removed) ("Michael Noto [MSFT]") wrote in
message | > Hi Joy,
| >
| > I am sorry but I did not see your posting until now. That message
indicates
| > a corruption of the database. The most common cause is the database was
| > opened in Access 2000 with the vbe6.dll file mentioned in the article
but
| > corruption may be caused by other circumstances also.
| >
| > I would suggest trying the steps in the article 304548 to recover as
many
| > objects of the database as possible.
| >
| > Another possible resource to recover datbase:
| > ===========================================
| > How to Troubleshoot and Repair a Damaged Access 2002 or later Database
| >
| > http://support.microsoft.com/default.aspx?scid=kb;EN-US;283849
| >
| > I hope this helps! If you have additional questions on this topic,
please
| > reply to this posting.
| >
| > Regards,
| > Michael Noto
| > Microsoft IIS Support
| >
| > This posting is provided 'AS IS' with no warranties, and confers no
rights.
| >
| > From: (e-mail address removed) (joydot)
| > Newsgroups: microsoft.public.access.gettingstarted
| > Subject: Re: Error Message: ErrorAccessing File. Network connection may
| > have been lost.
| > Date: 21 Jan 2004 07:22:21 -0800
| >
| > Michael Noto:
| > I have had this error occur, but I have Microsoft Office XP, not
| > Microsoft Office 2000. The Service Pack 3 only applies to Microsoft
| > Office 2000. Is there a fix for Microsoft Office XP?
| >
| > Thanks,
| > Joy
| >
|
 
Michael,
My concern is not the repair of the database; we have backups. Note
that I keep saying Microsoft Office XP, but you keep hearing Microsoft
Office 2000. The issue isn't with Microsoft Office 2000, but with
Microsoft Office XP. Microsoft Office XP Professional SP1 has the bad
version of the .dll as documented in the initial article. We have
corrupted the database with XP.

Thanks,
Joy
 
Hi Joy,

The version of the dll does not indicate that it is bad. Early builds of
Access 2000 are the problem. If you have that version of the dll and are
using access 2002 or 2003 then the corruption was not caused by the known
problem.

If any of the users are using Access 2000 with that version dll on the
computer and do not have the service pack listed in the article, the
corruption may occur. The 2000 msaccess.exe was the problem and is replaced
by a newer build which works correctly with the newer VBE6.dll when the
service pack is applied.

Regards,
Michael Noto
Microsoft IIS Support

This posting is provided 'AS IS' with no warranties, and confers no rights.

--------------------
| From: (e-mail address removed) (joydot)
| Newsgroups: microsoft.public.access.gettingstarted
| Subject: Re: Error Message: ErrorAccessing File. Network connection may
have been lost.
| Date: 30 Jan 2004 11:48:02 -0800
| Organization: http://groups.google.com
| Lines: 38
| Message-ID: <[email protected]>
| References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
| NNTP-Posting-Host: 137.100.73.40
| Content-Type: text/plain; charset=ISO-8859-1
| Content-Transfer-Encoding: 8bit
| X-Trace: posting.google.com 1075492083 27927 127.0.0.1 (30 Jan 2004
19:48:03 GMT)
| X-Complaints-To: (e-mail address removed)
| NNTP-Posting-Date: Fri, 30 Jan 2004 19:48:03 +0000 (UTC)
| Path:
cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.su
l.t-online.de!t-online.de!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!po
stnews1.google.com!not-for-mail
| Xref: cpmsftngxa07.phx.gbl microsoft.public.access.gettingstarted:144160
| X-Tomcat-NG: microsoft.public.access.gettingstarted
|
| Michael,
| My concern is not the repair of the database; we have backups. Note
| that I keep saying Microsoft Office XP, but you keep hearing Microsoft
| Office 2000. The issue isn't with Microsoft Office 2000, but with
| Microsoft Office XP. Microsoft Office XP Professional SP1 has the bad
| version of the .dll as documented in the initial article. We have
| corrupted the database with XP.
|
| Thanks,
| Joy
|
| (e-mail address removed) ("Michael Noto [MSFT]") wrote in
message | > Hi Joy,
| >
| > The latest SP for office 2000 does prevent the corruption from
occurring
| > when opening an version 2000 database using Access 2000 but applying
the SP
| > will not repair the database. If the database is only opened using
Access
| > 2002 or 2003 then the corruption is not caused by the steps to
reproduce
| > this error in the article below. Once the database is damaged, the
| > symptoms will occur in all versions of Access. The article has steps to
| > attempt recovering the forms, reports and modules of the database in
the
| > resolution section. Objects wihout code such as tables are not damaged
and
| > can be imported into a new database.
| >
| > Here is the article again:
| >
| > ACC2000: Error Message: Error Accessing File. Network Connection May
Have
| > Been Lost.
| >
| > http://support.microsoft.com/default.aspx?scid=kb;en-us;304548
| >
| >
| > I hope this helps! If you have additional questions on this topic,
please
| > reply to this posting.
| >
| > Regards,
| > Michael Noto
| > Microsoft IIS Support
|
 
Michael,
Ahhhh...now that makes sense. We do have customers moving their
database from one system to another, so they could be carrying the
potential for corruption with them.

Thanks for the help!! I consider this issue closed.
Joy
 
Glad to help!


--------------------
| From: (e-mail address removed) (joydot)
| Newsgroups: microsoft.public.access.gettingstarted
| Subject: Re: Error Message: ErrorAccessing File. Network connection may
have been lost.
| Date: 3 Feb 2004 15:01:56 -0800
| Organization: http://groups.google.com
| Lines: 26
| Message-ID: <[email protected]>
| References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
| NNTP-Posting-Host: 137.100.73.40
| Content-Type: text/plain; charset=ISO-8859-1
| Content-Transfer-Encoding: 8bit
| X-Trace: posting.google.com 1075849316 31891 127.0.0.1 (3 Feb 2004
23:01:56 GMT)
| X-Complaints-To: (e-mail address removed)
| NNTP-Posting-Date: Tue, 3 Feb 2004 23:01:56 +0000 (UTC)
| Path:
cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGXA06.phx.gbl!TK2MSFTNGXA0
5.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-online.de!newsfe
ed.gamma.ru!Gamma.RU!news.maxwell.syr.edu!postnews1.google.com!not-for-mail
| Xref: cpmsftngxa07.phx.gbl microsoft.public.access.gettingstarted:144382
| X-Tomcat-NG: microsoft.public.access.gettingstarted
|
| Michael,
| Ahhhh...now that makes sense. We do have customers moving their
| database from one system to another, so they could be carrying the
| potential for corruption with them.
|
| Thanks for the help!! I consider this issue closed.
| Joy
|
| (e-mail address removed) ("Michael Noto [MSFT]") wrote in
message | > Hi Joy,
| >
| > The version of the dll does not indicate that it is bad. Early builds
of
| > Access 2000 are the problem. If you have that version of the dll and
are
| > using access 2002 or 2003 then the corruption was not caused by the
known
| > problem.
| >
| > If any of the users are using Access 2000 with that version dll on the
| > computer and do not have the service pack listed in the article, the
| > corruption may occur. The 2000 msaccess.exe was the problem and is
replaced
| > by a newer build which works correctly with the newer VBE6.dll when the
| > service pack is applied.
| >
| > Regards,
| > Michael Noto
| > Microsoft IIS Support
| >
|
 
Back
Top