Compatibility issues

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a departmental accounting system that we have been using for about 10
years that is now running under Microsoft Access XP, but the backend
database, which resides on the server, it is still in the Access 2000 format.
We are having problems with losing a few line items for one specific
requisition number. We don't seem to have any problems with any other
requisition numbers or with any other parts of the program. Is there some
incompatibility issues because of backEnd is in an older format?
 
No. At least not anything that will cause that kind of issues. When it comes
to "missing" data, I often find one of the following to be true.

1. It was never there in the first place. It wasn't ever typed in OR entered
incorrectly so that it isn't showing up where it should.

2. It was there but someone deleted it.

3. It is there but the joins in queries are inner joins and the data won't
show up unless the related tables both have an entry.

4. There is a filter in a form or criteria in a query which causes the data
not to show.

5. You are using table-level lookups and that's confusing matters.

6. The database is corrupt or was corrupt. Make a copy and do a compact and
repair. It's possible that the in the past the database opened with an error
and suggested a compact and repair. In fixing the problem, some of the data
got deleted. Access should have mentioned that data was lost.
 
Well, this is a program that has been functioning now for 10 years as a
Microsoft Access database. It is split, with the backend residing on the
departmental server. The design of the database requires that a separate
database be used for each fiscal year. The program is used to reconcile
departmental financial records with the reports that come from the University
accounting office each month. For the last couple of months line items that
appear one month are "mysteriously" missing when the report is run the next
month. My boss is considering having a whole new system designed using SQL
Server so that we can have transaction tracking.

I know that the new version of Access has the capability of tracking
transactions IF you have everything installed that is required. But most of
my users are still using Windows 2000, so that is not an option. And we are
running on a Novell network anyway.

My boss was concerned that we were reaching the limits of the Access tables.
But the table in question has less than 10,000 records in it. So I know
that isn't the problem either.
 
Another thought just buzzed through the vacuum between my ears... Could you
possibly be linking to different backend database files by accident? I've
seen that before. Someone could be entering records in one .mdb file one day
then another the rest of the time.

Again I'd double check for inner joins on queries where there's missing
linking data from just one side. A right or left join would fix that.

Then there's corruption both at the database and people level. Since it's
financial records, someone might be messing with things....... If at the
database level, make a backup then do a compact and repair.
 
Is it that the data is not in the database or that it is not showing in your
forms/reports?

Are you working with an MDB or MDE?

Steve
 
Back
Top