"Error accessing file. Network connection may have been lost"

When trying to open a form in my DB, I get this error.

Everything worked fine, but then I pasted a form from another DB into the
current DB and now I get this error. This procedure used to work, but I have
just changed my computer - and on the new one I get this error. I am using
A2K on both PCs but the new one has XP as opposed to Win2K on the old.

There is no explanation in the help.

Any suggestions?

--
Diane

"DianePDavies" wrote in
message
When trying to open a form in my DB, I get this error.

Everything worked fine, but then I pasted a form from another DB into
the current DB and now I get this error. This procedure used to work,
but I have just changed my computer - and on the new one I get this
error. I am using A2K on both PCs but the new one has XP as opposed
to Win2K on the old.

There is no explanation in the help.

Any suggestions?

See this KB article describing the nasty bug that has bitten you:

http://support.microsoft.com/default.aspx?scid=kb;[LN];304548

Office 2000 SP3 fixes the bug, but that won't repair your corrupted
database. You'll have to resort to a backup, or else try importing all
objects to a new database -- some objects probably won't import, and
you'll have to recreate them from scratch. When you do import the
objects, unless you've applied the service pack, it is *crucial* that
you compile and save the project before closing the database.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

Problem solved! Thanks.

I thought scanning for Windows updates would prompt me to install Service
Packs on all MS-software... I had wondered though why I had not been asked to
do so. How can I do a total scan of all MS-software for possible updates?
--
Diane


"Dirk Goldgar" wrote:

"DianePDavies" wrote in
message
When trying to open a form in my DB, I get this error.

Everything worked fine, but then I pasted a form from another DB into
the current DB and now I get this error. This procedure used to work,
but I have just changed my computer - and on the new one I get this
error. I am using A2K on both PCs but the new one has XP as opposed
to Win2K on the old.

There is no explanation in the help.

Any suggestions?

See this KB article describing the nasty bug that has bitten you:

http://support.microsoft.com/default.aspx?scid=kb;[LN];304548

Office 2000 SP3 fixes the bug, but that won't repair your corrupted
database. You'll have to resort to a backup, or else try importing all
objects to a new database -- some objects probably won't import, and
you'll have to recreate them from scratch. When you do import the
objects, unless you've applied the service pack, it is *crucial* that
you compile and save the project before closing the database.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

"DianePDavies" wrote in
message
Problem solved! Thanks.

I thought scanning for Windows updates would prompt me to install
Service Packs on all MS-software... I had wondered though why I had
not been asked to do so. How can I do a total scan of all MS-software
for possible updates?

I think something like that will be coming someday soon, but for now you
would do well to visit

http://office.microsoft.com/en-us/of...e/default.aspx

(if you haven't already) to make sure that your Microsoft Office
programs, at least, are up to date.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)