Network connection may have been lost

[SuzyQ]

I received the error that network connection may have been lost. The problem
occurred after importing forms with code into the database. The problem
looks like the following KB article http://support.microsoft.com/kb/304548
problem, but I have Access 200 Professional not the standard edition the
article refers to. I have seen this before and followed the instructions to
copy the module's code, set the hasmodule property to no, and then paste the
code back to the module. It worked, fine, but this time I have over 100
forms and reports that I would have to do this to. I would rather start over
and import the forms/reports/modules again after having fixed the issue that
caused it to begin with. I'm unsure on how I should do that however.

 

[SuzyQ]

The reason for my post is that I've already - when this error occurred the
first time - installed SP3. Upon further investigation, it looks like both
the "business" and "professional" versions are installed on this machine.
Just confused on the different editions because the KB article says the
problem applies to the standard edition that does not have the service pack
installed. Not only do I not have the standard edition, but I do have the
latest SP, but I'm still experiencing the issue described and I need to know
how to resolve it so it does not happen again.

 

[Klatuu]

The various editions have nothing to do with Access. It pretains to the
edition of Office you have installed.

You don't say which version of Access you are usinging. There is no 200.
It would be 2000, 2003, or 2007. I am guessing you have 2003. If so, you
not only need Office SP3, but the SP3 HotFix.

The error that caused this problem usually means your database is corrupt.
Just porting the objects to a new database will probably not fix the problem.
Here are the steps you need to take:

For every form and report that has a code module you have to open the
module, copy the code to a .txt file, delete the code in the form, and set
the form's Has Module property to false.

For all code modules, copy the code for each module to a separate text file.

Open a new Access database.
Import all the tables, queries, macros, forms, and reports.

To get your code back, for each code module, create a new code module and
copy/paste the code from the old databse into the new module, name it the
same as the orginal and save it.

Same goes for the forms and reports. Open tje code module for each object,
and paste the original code into it.

Now compile your database and compact repair.

 

[SuzyQ]

the version is 2000 - I just left off a 0 somehow

As I said in my post, I did do what the article said to resolve the problem
and it did resolve the corruption in that database, however I had to import
again and that caused corruption again. I don't care about what I've already
imported because I can start over, which would be better than going through
100+ forms and reports to cut the code, set hadmodule to false, save, and
then paste the code back. Do I need the SP3 HotFix for Office2000?

 

[Klatuu]

If it is 2000, you should not install either SP3 or the hotfix for 2003
unless you have other 2003 Apps installed.

There really is not a better alternative to move the forms and reports. I
know it is tedious, but that is the way you need to do it.

 

[SuzyQ]

the KB article says that the problem/fix applies to 2000 and it also says to
install SP3. I have already installed SP3 - Do you think that is what caused
the corruption? If so, should I uninstall SP3? I have a good copy of the
databases in question. I want to resolve the issue so that when I import the
files again the data does not get corrupted again. That way, I can re-import
all the files and not go through fixing them. If I fix them and then import
another form or report, I will get corruption and have to go through this all
over again.

 

[Klatuu]

not enough info to determine what caused the corruption.
I would keep SP3 installed.

As to the corruption problem, there is a clue in this post. You talk about
having to import forms and reports because the data are corrupt. Does this
mean you have your tables in the same mdb as the forms and reports? If so,
you should not. Particulary if more than one person is using the application.

The correct configuration is that each user should have his/her own copy of
the front end (forms, reports, queries, etc) on there local hard drive. The
mdb with the data should be on a shared drive and each user should be linked
to the tables in that mdb.

If you have multiple users sharing the same front end mdb on a network
drive, you stand a very good chance of getting corruption.

 

[James A. Fortune]

the KB article says that the problem/fix applies to 2000 and it also says to
install SP3. I have already installed SP3 - Do you think that is what caused
the corruption? If so, should I uninstall SP3? I have a good copy of the
databases in question. I want to resolve the issue so that when I import the
files again the data does not get corrupted again. That way, I can re-import
all the files and not go through fixing them. If I fix them and then import
another form or report, I will get corruption and have to go through this all
over again.

If you are experiencing the problem that I only remember vaguely, then
even uninstalling SP3 is not going to help. If all else fails, such as
restoring the registry from before the SP3 install after you unistall it
or following Klatuu's advice and not getting results, then you might
have to reinstall the OS and stop short of installing SP3. Again, I
have only a vague memory of something like your scenario so I am not
sure my advice is what you need. In my case, the mdb with SP3 lost all
capability of converting an A97 mdb file into something that compiled.
Also, perhaps try a decompile on a backup of your mdb first. I have
seen mdb's that would corrupt beyond repair every time any form was
imported until a decompile was performed on the mdb (the backup copy
made before the import was attempted).

James A. Fortune
(e-mail address removed)

"You aren't gonna say you have a bad feeling about this, are you? I
hate it when you say that." - Han Solo

 

[SuzyQ]

I did not import the forms because the data was corrupt. I was in the
process of splitting a database so that forms and data were not in the same
database. I have multiple databases in which there were links to multiple
databases. I was attempting to create an FE application to consolidate the
user interface and separate the forms/reports/code from the data. It was
during this process that the forms got corrupted. If you look at the article
that I mentions - the cause and how to recreate the problem fit the scenerio
of what I was doing.

 

[SuzyQ]

Well, I ended up uninstalling office (professional and business) -
reinstalling office (professional only) I checked for dll mentioned in the KB
article (only one this time) then reinstalled SP 1, 2, and 3. I was then
able to import my forms and everthing seems to be working without a hitch. X
Fingers.

 

[Tony Toews [MVP]]

Well, I ended up uninstalling office (professional and business) -
reinstalling office (professional only) I checked for dll mentioned in the KB
article (only one this time) then reinstalled SP 1, 2, and 3.

For the future SP3 always includes the contents of SP1 and SP2.

Tony

 

[SuzyQ]

That's what I thought, but when I tried to install SP3, it said that the
required software was not found, so I installed 1 & 2, then was able to
install 3. and yes I did reboot after I reinstalled Office.