L
Lisa
Greetings! I am working with an Access 2000 database that I first
created about a year ago by converting an Excel "spreadsheet." My
predecessor knew nothing about Access, really, knew nothing about
Excel for that matter, and was using it as a database. It was a mess.
Anyway, at this point, the database has evolved to having 3 tables,
about a dozen reports, about the same number of queries, and a couple
of forms to make it easier for my two coworkers to use. The database
is housed on a drive on our campus' server. There are three users who
are working with the database on a daily basis, adding records and
making updates. Some reports are run several times a week, others
only 3 or 4 times a year. It currently holds about 4000 records, and
MANY fields of information. Periodically, too frequently for my
satisfaction, we will come up with error messages such as "that file
(fill in name) cannot be found, or is not a database", or "you or
another user closed the application without exiting" (even if I'm the
only one in the database, and I KNOW I clicked on Exit)... various
other messages, and records that end up corrupted (all fields w/ #
signs). The IT dept backs up the database about every other night.
Are there any tips that we can use to help minimize corruptions? We
really use the database for every aspect of our work, and a couple of
months ago we had to rebuild the database and import data from an old
backup (lost 3 weeks' worth of data...OUCH). I am wanting to avoid
that again. It does open up to a switchboard, and I am the only user
who actually sets up queries, reports, etc. (although the other users
don't have restricted access). Our IT support person suggested
setting up a front end/back end operation, and uploading changes every
evening. Only problem with that is that there are times when each
user might be working on a different aspect of a record right after
each other, and if current info is not there immediately after it's
input, it could cause mistakes in what the other users are doing.
Unfortunately, our IT support person assigned to help us knows as much
as I do about Access (which is not much!), and I have finally given up
on him. I figure I can go to the newsgroups and Microsoft's website
as easily as he can and do the same searches for info that he does.
Sorry this is SO long! I hope there's enough info here for someone to
provide some tips!
Lisa
created about a year ago by converting an Excel "spreadsheet." My
predecessor knew nothing about Access, really, knew nothing about
Excel for that matter, and was using it as a database. It was a mess.
Anyway, at this point, the database has evolved to having 3 tables,
about a dozen reports, about the same number of queries, and a couple
of forms to make it easier for my two coworkers to use. The database
is housed on a drive on our campus' server. There are three users who
are working with the database on a daily basis, adding records and
making updates. Some reports are run several times a week, others
only 3 or 4 times a year. It currently holds about 4000 records, and
MANY fields of information. Periodically, too frequently for my
satisfaction, we will come up with error messages such as "that file
(fill in name) cannot be found, or is not a database", or "you or
another user closed the application without exiting" (even if I'm the
only one in the database, and I KNOW I clicked on Exit)... various
other messages, and records that end up corrupted (all fields w/ #
signs). The IT dept backs up the database about every other night.
Are there any tips that we can use to help minimize corruptions? We
really use the database for every aspect of our work, and a couple of
months ago we had to rebuild the database and import data from an old
backup (lost 3 weeks' worth of data...OUCH). I am wanting to avoid
that again. It does open up to a switchboard, and I am the only user
who actually sets up queries, reports, etc. (although the other users
don't have restricted access). Our IT support person suggested
setting up a front end/back end operation, and uploading changes every
evening. Only problem with that is that there are times when each
user might be working on a different aspect of a record right after
each other, and if current info is not there immediately after it's
input, it could cause mistakes in what the other users are doing.
Unfortunately, our IT support person assigned to help us knows as much
as I do about Access (which is not much!), and I have finally given up
on him. I figure I can go to the newsgroups and Microsoft's website
as easily as he can and do the same searches for info that he does.
Sorry this is SO long! I hope there's enough info here for someone to
provide some tips!
Lisa