Query dumps memo text

[jessa]

I have my query set up to include a "synopsis" field that I have set as memo. For some reason when the query is ran, all but one to two sentences of the memo field is deleted. When I go back to the table, or form the entire text is still there. Any help is greatly appreciated..

Thanks,
Jessa

 

[Newman]

I just happen to have the same trouble.
To me, it only happens to Oracle memo fields though.
I also found out that the field is not truncate when the memo field is the only field in the query.

Is it the same with you? That might give us a hint on where to look for answers.

Please, come back if you find anything. I will.

 

[Newman]

I found two threads that gave answers to our problem. I've tried them both and it didn't work for me, but here it is in case it works for you.

-A lack of memory: Your query is very complex and/or there is a lot of running applications and/or there is not enough of memory in your computer.

-You use a lot of criteria in your query and/or a criteria in your memo field.

 

[jessa]

Maybe..

Thank you, I will try it out and see if it works. This may well be the problem, as I spent the weekend rebuilding the db and it worked great, as soon as I shut down and restarted then I was having the same problem again.

 

[The_Doc_Man]

I'm not clear on your exact problem. Please clarify a fine point. When you say,

For some reason when the query is ran, all but one to two sentences of the memo field is deleted.

Do you mean that the source table that contains the original memo field is actually modified or is it that your query just doesn't report (i.e. OMITS) some sentences? This makes a big difference in how to treat the problem.

In the former case, you are populating a table from another data source with an UPDATE or INSERT query. In the latter case, you are merely running a SELECT query that has gone awry. Need to know just a little bit more details, if you can provide them.

 

[jessa]

I am running a select query, the data in the memo field is omitted with the exception of a couple sentences. The data in the actual table that the query is pulling the information from is kept in tact.

 

[The_Doc_Man]

Another poster in this sub-section of the forum reported a similar problem, for which his solution was to delete the query and rewrite it from scratch.

Don't know if that would help.

Access gets kinda "hinky" about MEMO fields because it has to treat them specially. (That's why you cannot sort on them.) I'm wondering if something has confused it. Which is why a complete rewrite might work.