Cell contents over 1024 characters will not center or right align

[wilkisa]

Excel 2013. My user has a cell in which he enters contract numbers one after another in the single cell, ie., 123456, 234567, 345678, etc. The cell is 15 characters wide and the default height. He does not want the cell size changed. Each day, or several times a day, he has to add a new contract number to the end of the list. When it was still a reasonably short list, the cell would always display the last number in the list. He could then F2 and add the new number to the end which was then visible in the cell. He has discovered that, as time has passed that he is no longer seeing the last contract. Instead, he is seeing the number that is at the 1024 character mark (his cell has 2453 characters). His alignment is Right-Indent. Changed to Center alignment and it focuses on the midway point between 1 and 1024.

This isn't a show-stopper but more a curiosity. Can someone explain why it performs this way?

 

[mole999]

https://support.office.com/en-us/ar...d-limits-1672b34d-7043-467e-8e27-269d656771c3, in a local cell that isn't being updated maybe =RIGHT(activecell,6) so it can be viewed

 

[wilkisa]

Thank you for your reply but I'm not sure what you want me to see in the link provided. I know the cell limitations are not being met so that shouldn't be an issue. We don't want to add yet another cell in this document as it is a form his department uses and they won't allow structure modification. The issue is really very simple, though. When the cell contents are less than 1024 and alignment is RIGHT (INDENTED), the last item in the text displays perfectly in the cell without resizing it. Once the content is more than 1024, it will not display the additional data regardless of alignment. Again, this isn't a show stopper but more a curiosity and annoyance.

 

[mole999]

probably a bug that is not known about and i can't think of a reason to keep incrementing to the right (beyond that is happening here)

 

[wilkisa]

Yes, Mole999, I concluded that it was a bug that is not high on the priority fix list. I just hoped that maybe it was something I was overlooking. I appreciate your responses, however, and am glad someone else sees it the same way I do.