Re: problem with 2003 reports not matching
- From: "Allen Browne" <AllenBrowne@xxxxxxxxxxxxxx>
- Date: Tue, 12 Jul 2005 10:57:49 +0800
First thing to check is that the machines are all connected to the same data
file. You would not be the first to strike this kind of issue when some
machines are connected to a different back end file.
Next, open the back end, and try a repair:
Tools | Database Utilities | Compact And Repair
If the date field is indexed, and the index is damaged, this should fix the
problem.
There is actually a hotfix out that addresses records missing in a report in
A2003 after SP1 has been applied. Not sure this sounds like your issue, but
details at:
http://support.microsoft.com/default.aspx?scid=kb;en-us;840656
If that does not solve the issue, double-check that the Name AutoCorrect
boxes are unchecked in all databases (the back end, and each front end)
under:
Tools | Options | General
It is possible for Access to misunderstand the basic names in the query if
this misfeature is on. More info:
http://allenbrowne.com/bug-03.html
Then compact again.
If the problem persists, the next thing to look for is different versions of
JET on the machines that return different results. JET is the query engine
in Access. Locate the file msjet40.dll, typically in \windows\system32.
Right-click it, and on the Version tab you should see 4.0.8xxx.0. The xxx
digits don't matter, but if you don't see the 8, download JET 4 SP 8 from:
http://support.microsoft.com/gp/sp
If you are still stuck, does the source query for the report return the
correct number of records?
- No: the problem is with JET drawing in the data. Post the SQL statement.
Check the service packs on the server.
- Yes: the problem is with the report presenting the data (e.g. code in the
report's events.)
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Chris Cowa" <chris.cowan@xxxxxxxxxxxx> wrote in message
news:uM9Q%23ilhFHA.2424@xxxxxxxxxxxxxxxxxxxxxxx
>I have an unusual problem. I have a DB that is split. It was created
> originally in Access 2000. We are now a mixed house of 2000 and 2003. The
> BE
> is on a server; wheras the MDB/MDE is on the users PC.
>
> Here is the problem.
>
> I have a report that runs that selects if a date is over due. In 2000 it
> shows 7 records, in 2003 it shows 5 records. Now here is the funny part. I
> have a test machine with XP OS and Access 2003 on it. It shows all 7
> records. whereas I have a Technician build 50 others that is similar. The
> report runs good on mine (7 records).
>
> I am trying to determine where in his setup that is different then mind.
> It's blowing my mind.
>
> I can take the same MDB and place on my 2000 system, my 2003 system and
> someone elses 2003 system. In the first 2 I get 7 records; in someone
> elses
> I get 5 records.
>
> Help
>
> Chris
.
- Follow-Ups:
- Re: problem with 2003 reports not matching
- From: Chris Mills
- Re: problem with 2003 reports not matching
- References:
- problem with 2003 reports not matching
- From: Chris Cowa
- problem with 2003 reports not matching
- Prev by Date: Re: problem with 2003 reports not matching
- Next by Date: Re: problem with 2003 reports not matching
- Previous by thread: Re: problem with 2003 reports not matching
- Next by thread: Re: problem with 2003 reports not matching
- Index(es):
Relevant Pages
|