anomaly in one of my reports

  • Thread starter Thread starter ngan
  • Start date Start date
N

ngan

I have Access XP FE and SQL 2k BE.

For the past few weeks, one report has been running just
fine....but then yesterday, the person who prints it out
noticed an anomaly.

Here is what the report does:

I have two tables, complaint and response. The report
looks at a query where it lists all the complaints and
response in a LEFT JOIN (complaint -> response). The
criteria looks at two fields in the response table,
ResponseReadyDate (is not null) and ResolutionDate (is
null).

Yesterday's printout of the report listed complaints that
didn't have responses. When I ran it today, those didn't
show up. I haven't been able to recreate the anomaly. I
don't know how those complaints would have shown up
because my criteria asks for ResponseReadyDate that is not
null. If those complaints never had a response record,
the dates would be null.

Anyone dealt with this before?
 
"Null" and "not Null" don't always work the same with server databases as
with Access -- I discovered that in an Access client to Informix. I don't
recall having similar problems with Microsoft SQL Server, but it's a
thought.

Maybe someone who's deeper into Access clients to Microsoft SQL Server can
tell us if this is also the case in environments similar to yours.

But, it seems surprising to me that it would just happen _once_ and then
work OK, again. Could anyone have changed the Query in that copy of the
Access client? Have you tried rerunning the Report with yesterday's
selection criteria to see if that will reproduce the problem?

In the meanwhile, are you current on SPs for Office XP? I believe there are
3. There are 8 SPs for the Jet database engine if you are connected via
Jet-ODBC. Also, you might want to see if the SQL Server is current on
Service Packs/patches.

Larry Linson
Microsoft Access MVP
 
Back
Top