###### appears in table fields

[BJS]

Users of one of the Access 2000 databases that I support have encountered a problem:

2 records in the table have been overwritten with "###############" in each of the fields.

Anyone know what causes this?
I found an Article on the MS Knowledge Base (274211), it talks about multiple users editing a memo field at the same time, and that setting the Default Record Locking option to "Edited Record" will solve the problem.

In this particular database, none of the fields in this table are memo fields. Not sure if this matters or not.

Any suggestions or comments? Thanks.

 

[llkhoutx]

Column width in the table view is too small. Drag the heading border to widen the field, or simply double-click it.

 

[BJS]

Thanks for that, but this is not the case.
Widening the columns to fit the contents does not solve the problem.

The # signs are also in every field for the two records affected.
Also I am not able to search for the data that was contained in these fields. I know what the values were, and they have simply been overwritten with ###########.

Any more ideas?

 

[llkhoutx]

Maybe the "Format" property of the fields being imporperly displayed has been set to an improper value.

 

[BJS]

I will check on that tomorrow (don't have access to the db today).

But I'm not sure how the format of the field can be an issue, since the values for the same fields appear fine for all the other unaffected records.

???

 

[llkhoutx]

another possibility is that the two records are corrupted. Write a little routine to display every field in those records.

 

[SQL_Hell]

Yep, I go with the corruption comment by llkhoutx

I have experienced this kind of corruption before on memo fields,

I would lock the text boxes on the forms that hold memo fields, and give the user a button to make an edit on that field if they need to.

or

you could get into persimistic locking, but i wouldn't advise it in access.


Hope this helps

SQL_Hell (new member today!)

 

[BJS]

Thanks to both of you, llkhoutx and SQL_Hell!

I will have to say the records got corrupt.

BJS.