Hieroglyphics in my Memo field

[Nona]

This group has pulled me out of trouble several times, and I hope at least
once more!
On a table in my new database, I have a memo field for comments. While no
data has actually been entered, the report that displays the comments shows
about 1/4 inch of strange-looking type at the beginning of the comment
section.

As a test, I entered a few words, and that did not display at all - just the
hieroglyphics. Thinking that the field was corrupt, I created a new table,
then copied and pasted all the data from the old table into the new one.
Except I did not copy the comment field from the old table. However, I still
get the same result. It will not print an actual statement that is showing on
the table. Very strange!

Any idea what could cause this, and how I can fix it?

Thanks,

 

[a a r o n . k e m p f]

it's called database corruption!!!! Ding-Ding-Ding!!

I'd guess that you have 'too many people' or 'too many records' for
Access to use reliably.

it's best to move to SQL Server in order to prevent these problems

 

[Pete D.]

As you didn't bring the old memo into the new datafile I would carefully
inspect the source for the report, query/vba/sql if involved, memo field
formating on the report and check the report in design view.

 

[Nona]

Thanks for your suggestions. I had assumed the problem was with the table,
but after I created a new query, it works perfectly!

Thank You!

 

[Pete D.]

Great, take care, Pete

Thanks for your suggestions. I had assumed the problem was with the table,
but after I created a new query, it works perfectly!

Thank You!

 

[Aaron Kempf knows nothing]

it's called a a r o n . k e m p f corruption!!!! Ding-Ding-Ding!!

 

[a a r o n . k e m p f]

don't stalk me asshole

 

[Arvin Meyer [MVP]]

It most likely was corruption, and I'd do several Compact and Repair
operations, then I would import everything into a new clean empty database.

Memo fields are the first to corrupt because they are OLE fields and the
data is actually stored in a different area of the database. Since they are
stored in a different area of the database, any interruption during a write,
can dislocated the pointer which is an index.

It is a good idea to store memo field data in its own table with a primary
key connection to the main table. That way, the worst that will ever happen
is that you will lose just the memo data, and not the entire row or table,
or in a worst case scenario, the entire database.