No subject

Wed Dec 28 11:38:03 CST 2011

Rocky Smolin
Beach Access Software

----- Original Message -----=20
From: Joe K Anderson=20
To: Joe Anderson ; Barry Hynum ; Bob Heygood ; Dixon Foss ; Ed Lance ; =
Greg Otero ; Rocky Smolin ; Tim Henning ; Wayne Warren-Angelucci=20
Sent: Monday, March 17, 2003 11:03 PM
Subject: Fw: Feb 2003 Access-VB-SQL, pg 10 'Database Problem'

Guys ... FYI ....

joe

----- Original Message -----=20
From: Joe K Anderson=20
To: mikegroh at earthlink.net=20
Sent: 03-17-2003 23:02
Subject: Feb 2003 Access-VB-SQL, pg 10 'Database Problem'

Hi Mike ...

Thanks for continuing to be involved with a high quality magazine like =
Access-VB-SQL.  In fact I have every issue since day one.

Regarding the "Error Accessing File.  Network Connection may have been =
lost" problem:

The good news is that is has nothing to do with networks, split MDB's, =
LDB's etc.  It's a totally bogus error message. =20

The bad news is the mdb is *usually* corrupted beyond repair ... even =
the 'decompile' trick does not fix it, nor does the JetComp utility.  =
The code behind a form(s) and/or code in a VBA module(s) is corrupted.  =
Odd, because Decompile fixes about 99% of all VBA corruption problems

In Office 2000, there is a certain version of the Vbe6.dll that causes =
the problem

This knowledge base article gives all the details.

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

I indicated *usually* above because I was never able to fix the =
corruption with any trick I was aware of.  I don't recall the original =
KB article discussing any resolutions ... just mentioning the DLL and to =
get Office 2000 Service Pack 3 ... which *did* fix the problem. =20

The bottom line usually was just as Microsoft states at the bottom of =
'RESOLUTION':

"If you do not have a computer without the version of Vbe6.dll mentioned =
in the "Cause" section, you must revert to a known good backup copy of =
the database. To prevent this problem from happening again, use one of =
the following methods, depending on which version of Access you are =
using."

BTW .. neither of the 'Methods' mentioned were 100% reliable!!

Anyway ... since I've had first hand experience with this ugly problem =
.. I thought I would pass this info on to you.

Joe Anderson
AllData, Inc.
www.alldatacorp.com
858.270.4400
------=_NextPart_000_00CB_01C2ED35.BBB89140
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1141" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>From a friend.  FYI.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Rocky Smolin<BR>Beach Access =
Software</FONT></DIV>
<DIV> </DIV>
<DIV style=3D"FONT: 10pt arial">----- Original Message -----=20
<DIV style=3D"BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> <A=20
title=3Dja at alldatacorp.com href=3D"mailto:ja at alldatacorp.com">Joe K =
Anderson</A>=20
</DIV>
<DIV><B>To:</B> <A title=3Dja at alldatacorp.com =
href=3D"mailto:ja at alldatacorp.com">Joe=20
Anderson</A> ; <A title=3Dbhynum at cox.net =
href=3D"mailto:bhynum at cox.net">Barry=20
Hynum</A> ; <A title=3Dbheygood at abestsystems.com=20
href=3D"mailto:bheygood at abestsystems.com">Bob Heygood</A> ; <A=20
title=3Dfossware at gte.net href=3D"mailto:fossware at gte.net">Dixon Foss</A> =
; <A=20
title=3Delance at san.rr.com href=3D"mailto:elance at san.rr.com">Ed Lance</A> =
; <A=20
title=3Dgreg at sundancesoftware.com =
href=3D"mailto:greg at sundancesoftware.com">Greg=20
Otero</A> ; <A title=3Dbchacc at san.rr.com =
href=3D"mailto:bchacc at san.rr.com">Rocky=20
Smolin</A> ; <A title=3Dhenningt at san.rr.com =
href=3D"mailto:henningt at san.rr.com">Tim=20
Henning</A> ; <A title=3Dwayne.warren at adelphia.net=20
href=3D"mailto:wayne.warren at adelphia.net">Wayne Warren-Angelucci</A> =
</DIV>
<DIV><B>Sent:</B> Monday, March 17, 2003 11:03 PM</DIV>
<DIV><B>Subject:</B> Fw: Feb 2003 Access-VB-SQL, pg 10 'Database=20
Problem'</DIV></DIV>
<DIV><BR></DIV>
<DIV><FONT size=3D2>Guys ... FYI ....</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>joe</FONT></DIV>
<DIV> </DIV>
<DIV style=3D"FONT: 10pt arial">----- Original Message -----=20
<DIV style=3D"BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> <A=20
title=3Dja at alldatacorp.com href=3D"mailto:ja at alldatacorp.com">Joe K =
Anderson</A>=20
</DIV>
<DIV><B>To:</B> <A title=3Dmikegroh at earthlink.net=20
href=3D"mailto:mikegroh at earthlink.net">mikegroh at earthlink.net</A> </DIV>
<DIV><B>Sent:</B> 03-17-2003 23:02</DIV>
<DIV><B>Subject:</B> Feb 2003 Access-VB-SQL, pg 10 'Database=20
Problem'</DIV></DIV>
<DIV><BR></DIV>
<DIV>Hi Mike ...</DIV>
<DIV> </DIV>
<DIV>Thanks for continuing to be involved with a high quality magazine =
like=20
Access-VB-SQL.  In fact I have every issue since day =
one.</DIV>
<DIV> </DIV>
<DIV>Regarding the "<STRONG>Error Accessing File.  Network =
Connection may=20
have been lost"</STRONG> problem:</DIV>
<DIV> </DIV>
<DIV><FONT size=3D2>The good news is that is has nothing to do with =
networks,=20
split MDB's, LDB's etc.  It's a totally bogus error =
message. =20
</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>The bad news is the mdb is *usually* corrupted =
beyond repair=20
... even the 'decompile' trick does not fix it, nor does the JetComp=20
utility.  The code behind a form(s) and/or code in a VBA module(s) =
is=20
corrupted.  Odd, because Decompile fixes about 99% of all VBA =
corruption=20
problems</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>In Office 2000, there is a certain version of the =
Vbe6.dll=20
that causes the problem</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>This knowledge base article gives all the=20
details.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2><A=20
href=3D"http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;304548"=
>http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;304548</A></FO=
NT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>I indicated *usually* above because I was never able =
to fix=20
the corruption with any trick I was aware of.  I don't recall the =
original=20
KB article discussing any resolutions ... just mentioning the DLL and to =
get=20
Office 2000 Service Pack 3 ... which *did* fix the problem.  =
</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>The bottom line usually was just as Microsoft =
states at=20
the bottom of 'RESOLUTION':</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><EM>"If you do not have a computer without the version of Vbe6.dll=20
mentioned in the "Cause" section, <STRONG><FONT color=3D#ff0000>you must =
revert to=20
a known good backup copy of the database</FONT></STRONG>. To prevent =
this=20
problem from happening again, use one of the following methods, =
depending on=20
which version of Access you are using."</EM></DIV>
<DIV><EM></EM> </DIV>
<DIV>BTW .. neither of the 'Methods' mentioned were 100% =
reliable!!</DIV>
<DIV><EM></EM> </DIV>
<DIV>Anyway ... since I've had first hand experience with this ugly =
problem=20
.. I thought I would pass this info on to you.</DIV>
<DIV><EM></EM> </DIV>
<DIV><FONT size=3D2>Joe Anderson<BR>AllData, Inc.<BR><A=20
href=3D"http://www.alldatacorp.com">www.alldatacorp.com</A><BR>858.270.44=
00</FONT></DIV></BODY></HTML>

------=_NextPart_000_00CB_01C2ED35.BBB89140--