Dbase is acting erratically

[Frustrated]

I was receiving the error message "Error accessing file, network Connection
may be lost", so per the groups responses to other users I had service pack 3
installed on my PC and then rebuilt the Dbase from scratch.
Now, the Dbase is doing strange things.
1.) It will not let me create a switchboard, or should I say it will not
allow me to create a switchboard that actually opens forms.
2.)If I copy a form and try to paste it as a new form with a new name I
receive the message that a form with that name already exists....when it does
not. Not only does it not exist a form with the new name has never existed.
3.)When I try to import a form from another Dbase I go through all the steps
and it appears the import went smoothly however the objects do not import.

There are other peculiarities going on, but I can't think of them right now.

Also you should know that yesterday I had IT re-install windows and office
with the hopes that it was my PC but I am still having the same problems. I
am on Windows 2000 and Office 2000. My PC is connected to a network, but the
Dbase is sitting on my local drive.

Any idea what might be causing this or how I fix it?

 

[Frustrated]

I should also add that even though I have installed service pack three and
rebuilt every object in Dbase (did not import anything from corrupt Dbase) I
am still receiving the "Error accessing file, network connection may be lost"
error.

 

[Allan Murphy]

I have experienced this a few times when developing databases on a network.
This is caused by a fleeting lost of connection.

To overcome this I created a blank database then imported tables from the
faulty database then did queries etc During the import you may receive a
message saying object corrupt or something similar. I suggest you import a
small number each time, that way you will have a better idea where the
corrupt object is.

Now I develop my database on a "stand-alone" or laptop or if I use the
network for developing I save a copy of the current database then rename the
current database. I may start out with databasename_001.mdb then save it
usually in a ZIP or 7zip format after I have tested the latest changes then
rename the database as databasename_002.mdb so that if I have problems I
know the previous version is OK

HTH