Odd Report Behavior (Access 2002)

Topic

New Reply

Hey All!

I have a report in Access 2002 that is based on a query. The query that displays the data isn’t too complicated, and the report isn’t too complicated. When I first open the database and run the report, some of the data does not display.

If I close the report and open it again, all of the data displays. It’s very odd and rather random, although it seems to happen more frequently when you first open the database. It doesn’t seem to matter if you do this with the subreport alone, or from the main report.

I’ve searched MS for this, but haven’t seen anything about updates to Access or Office that would fix this problem.

Has anyone had this problem before? Any ideas on how to fix it?

TIA!

Reply | Quote

Replies

This sounds like something is amiss with your database. Are the tables in the same database as the report (and it’s datasource query)? If so, you might try importing everything into a new empty database. On the other hand, if the tables are in another database, what is that database? You could be seeing some sort of weird ODBC problem for example.

Reply | Quote

Hi Wendell–

It’s a backend/frontend setup, where both the back end and front end are Access2002. (The back end does link to a whole bunch of SQL server and db2 tables, but only for downloading purposes, which we’ve not yet had any issues with. There is no case where the SQL server or db2 tables are used for anything in the front end, and they’re only used in the back end to download data, not to display it.

The front end links to all of the back end tables (the ones that contain the data that was downloaded from the SQLServer/DB2), but all the queries are in the front end. It doesn’t seem to be a data issue, because I don’t get this behavior at all running the queries. But would a report problem be so inconsistent?

Originally I thought it might be a corruption issue. When I started this project, I created an Access 2000 database in Access 2002 and went back and forth between developing in 2002 and 2000 (because “they” wouldn’t let me install 2002 on my laptop ;-), but most of it was done in 2002. Apparently we’ve been having this “disappearing” issue all along, I was just the last one to notice it.

Anyway, yesterday I upgraded both the back end and front end to 2002, and did the import thing into a new database, but neither one seemed to help.

Any idea what to try next?

Reply | Quote

I frankly almost never work with the 2002 format as most clients have 2000 installed, so it’s possible there’s something weird going on there. Have you managed to get the same behavior in 2000 with a database where you import all of the objects into an empty 2000 database? We have seen a few weirdities when you develop in 2002 and then deploy it to 2000. Since the query is returning the correct recordset repeatedly, it sounds like it could be a problem with the report itself, and not a problem with the database engine. You could try creating a simple report and see if it works correctly.

Reply | Quote