Dates stopped

  • Thread starter Thread starter Laney
  • Start date Start date
L

Laney

I am working a project with a huge database in access. The person that
created it is no longer with the company and not willing to help with
anything.

The queries just stopped feeding any information down the line after
September 28, 2008. I have gone through tons of tables and queries on all of
the databases to see if there's something set up stating (criteria) to only
pull up before that date and have found nothing. No requirements for any
dates are set.

They have multiple databases and each databases have thousands of records
like in the 50 to 70 thousand entries range. The only thing I have noticed in
common at all is that most of them "link" the tables from the same databases.
Then queries are built off of that.

Is the database just getting too big?

Do I need to compact and repair?

Any suggestions at all would be greatly appreciated.

Thanks!
 
"> The queries just stopped feeding any information down the line after
September 28, 2008."
Click to expand...
What exactly do you mean?
Can you run the queries?
What happens when you do?
You need to analyse this one step at a time.
Find one query that is not working, run it as a standalone query and see
what happens. Often people will put hard-coded dates in queries which need to
be changed when another fiscal year comes around.
If the database is too big, normally you will get some type of error message.
Make sure you make a backup of the database before you start messing with it
- particularly if you are unsure what you are doing.

-Dorian
 
Thanks Dorian, I just received some other information that totally changed
everything. So I'll check into it. :) Have a great evening!
 
Is the database just getting too big?
Click to expand...

How big is it? Check the size of the .mdb file in Windows Explorer: if it's
above (or approaching) 2GBytes, then yes it's too big.

In any case, *make a backup*, open the database, and use Tools... Database
Utilities... Compact and Repair.

Is it possible that this previous employee was sufficiently disgruntled to
leave a timebomb in the database design?
 
Back
Top