Hi George,
I'm not familiar with using "a diginet to connect to the server". Is your
database split into two .mdb files: a front-end (FE) and back-end (BE)? The
BE contains only the tables with the shared data; this is the file that is
copied to the file server. The FE contains all other objects. A copy of the
FE should be placed on each user's hard drive. If you have not done this,
then you should know that Microsoft has identified sharing an entire database
as the #1 cause of corruption.
As Arvin indicated, Access will create a backup if it crashes. You can also
get backup copies if a compact operation fails. Now would probably be a good
time to create a new database, and then import all objects, one group at a
time, into your new database. In other words, import all tables (but not
linked tables), then import all queries, then all forms, etc. While Access
will allow you to import all objects in one operation, the experts at FMS,
Inc. (a Microsoft Partner), have stated that it is best to import objects one
group at a time. Recreate any linked tables from scratch. When importing
local tables, make sure to check the option to import relationships, menus
and toolsbars, and import/export specs. If any of the local tables in the
source DB are hidden, you'll need to first unhide them.
You will need to set the checked references to match the source database,
along with any startup options set under Tools > Startup. You should disable
Name Autocorrect after creating the new container database. Going through
this process often times solves corruption problems, because you get a new
set of the hidden system tables (the tables whose names start with "MSYS").
These system tables are updated appropriately as you import objects.
This may sound like a lot of work, but it really isn't. Creating a new
container DB, disabling NameAutocorrect, importing all objects one group at a
time, and setting startup options and references to match the source DB is
usually a fairly quick procedure. When you are in the Visual Basic Editor, in
order to check that the references match the source DB, you should do a Debug
Compile ProjectName as well. You want to re-create any linked tables from
scratch, because Access can cache a lot of information about the links. Some
of this infomation may no longer be valid, so it's always best to recreate
the linked tables from scratch.
Good Luck,
Tom
____________________________________
:
no errors it just makes a file called back_up which never happend before, i
think it might have something to do with the network because the people who
access it are in another building and use a diginet to connect to the server
to get to the database.
can this cause delayed problems so it backs itself up when i recognisers a
problem?
____________________________________
:
Hi George,
Do you have the Compact on Close option set under Tools > Options... |
General tab ? If so, I suspect that every time you attempt to close the
database, the compact operation fails for some reason. This could be a sign
of possible database corruption. Try compacting the database manually:
Tools > Database Utilities > Compact and Repair Database...
Do you get any kind of error message and/or is a back-up file created in the
process?
Tom
____________________________________
:
4 some reason unknown to me my data base makes a back_up by itself several
times a day? a places it in the same folder where the data base is kept how
do i stop it???
