db errors in access

[Zoey Beloshchenko]

Good Morning,
I have created a database and the forms to run it solely
in access and it has been stored on my office's networked
drive. I also have it back up on my local drive.

It's running fine on my local drive and up until today,
ran fine on the networked drive. But as of today I get an
error. I can open and manipulate the program fine but
when I close it down I get the error that I am referenced
an unknown field known as "description". I have checked
all the tables and forms and there is no such field.

Also when I got back into the network drive I see not only
the program but also db1, db2, db1.ldb etc. One for each
time I have closed the program down.

Any ideas as to what is wrong and how do I fix it?
Thank you in advance,
Zoey Beloshchenko

 

[Zoey Beloshchenko]

I hope it doesn't come to that.
I tried deleting the the database on the network and then
copying the database from my local drive to the network.
Same problem. I just don't understand what's going on
because the app is still working fine on my local drive.
Zoey

 

[Steve Schapel]

Zoey,

I hope it doesn't come to that.

Why not? Very simple 2-minute job.

- Steve Schapel, Microsoft Access MVP

 

[Zoey Beloshchenko]

I've already tried deleting and recopying with no
success. It runs fine on my harddrive but not on the
network.

Anyway, I did have the app set to compact and repair on
close. I've removed that and now eveyrthing seems to be
running fine, so far.
Thanks for the help,
Zoey

-----Original Message-----
Zoey,

I agree 100% with Elwin's suggestion.

You might also look at applying the JetComp utility (refer to
http://support.microsoft.com/?id=273956 )

In addition, if this is an Access 2000 or Access 2002 database, and
you have the 'Compact On Close' option enabled, I would avoid using
this feature if the database is networked. Would you look into the
possibility of splitting the database so that the core data tables are
in a linked database on the network drive, and the rest oh the local
drives of the users?

- Steve Schapel, Microsoft Access MVP

 

[Steve Schapel]

Zoey,

Pleased to hear that the situation has improved.

However, if it was mine, I would still rebuild the database file.
Make a new .mdb database, go to File|Get External Data|Import menu,
locate your existing database file, select all objects, click the
Options button and set to include Relationships, Toolbars,
Import/Export Specifications, etc, and then import. Recompile your
code, Compact/Repair, and then rename and replace the existing file
with this new one.

- Steve Schapel, Microsoft Access MVP

 

[Zoey Beloshchenko]

If you think that's best, then that's what I'll do.
Just to be safe.

Thanks for the help.
Zoey