memo in Access report

base the report on the query taht contains the memo. It is much better to run reports based on queries as data source. if the query runs ok but your only problem is the report , re do the report using the query as the data source

Most probably your report is accessing a large file. One solution you can do is create a make table query using the 2 queries that you have and then use the resulting table as your datasource for the report. If you have a print button, insert the make table query before you open the report in the on_click event procedure.

I took the report, modified, down one level of query and got the same failure. When I pruned the lower query the memo started coming through. Eventually I got all the information by putting the inner join at the center of the lower query int a yet lower query, and I was able to pass all the information upwards to the report at the top of the nest. If there were a Microsoft representative in the shop I would be negotiating a transfer of the problem, but there isn't and I do not intend to do any more investigating unless someone suggests a probably fruitful line. There is obviously a fault in the report processing, probably awoken by a fault in JET, the SQL engine.

You don't mention the number of records in the tables involved in the queries. This certainly can be a factor in the response of your system. If you are talking about, say, 100,000 records or more with a memo field part of every record, the amountof data could be part of the problem.

Are your primary keys and indexes set up in ways that will make your queries run efficiently? While this can just slow down your database somewhat, when the queries also include memo fields, the slowdown canbe dramatic.

Are you attempting to select records based on data in the memo field? I haven't had problems displaying/printing reports with memo fields. BUT...if I tried to select records (whether for display on a form or for a report) by finding a match to text in a memo field, things could come to a grinding halt.

There isn't an easy solution to searching memo fields. Ideally, you can set up a text field (255 characters) where pertinent data (ex: summary description, or keywords) of the contents of the memo field will be entered. Searching for a text match in the text field should run at a reasonably good speed.

You might want to provide descriptions of the tables and queries involved to help us better understand what is going on.

The effective solution has been to nest the table containg the memo a little deeper. On day I must learn about how Access actually works.

This question was closed by the author