Error-Network Drive lost

[wjbrow]

I have a database program that was working fine until I lost my hard drive
when I reinstalled a copy I am recieving an error of Network connection may
have been lost. The program only have files on a local drive. How can I
correct his problem without declaring all my variable public?

 

[Dirk Goldgar]

I have a database program that was working fine until I lost my hard
drive when I reinstalled a copy I am recieving an error of Network
connection may have been lost. The program only have files on a local
drive. How can I correct his problem without declaring all my
variable public?

I can't tell for sure, but you may have fallen prey to a bug in Access
2000 (if that's what you're using). See if this Microsoft KnowledgeBase
article describes your situation:

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

If it does, 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.

 

[wjbrow]

Thanks Dirk, It sounds as if your solution addresses my problem exactly. I
will reserve jugement on it after I see if it reslves my issue. I could take
some time to complete the steps spelled out. I will follow up this reply when
I complete the process.
Bill
You have been very helpful.

I have a database program that was working fine until I lost my hard
drive when I reinstalled a copy I am recieving an error of Network
connection may have been lost. The program only have files on a local
drive. How can I correct his problem without declaring all my
variable public?

I can't tell for sure, but you may have fallen prey to a bug in Access
2000 (if that's what you're using). See if this Microsoft KnowledgeBase
article describes your situation:

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

If it does, 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)