HTML strings are getting corrupted at the ends.

VBA routine, that formats a string of HTML, that has been working for years, suddenly started throwing strange ASCII codes at the end of strings in apparently random records.

The 1st attached pic is a screen shot of the output, all ok until the last row.
The 2nd attached pic is a screen shot of the output, just the errors in the first 120 of 211 records.

Doesn't seem to relate to the length of the string it's stringing together ("EntityNamesDisp"), but it does seem to happen at the ends of the strings.

Sorry to post such a vague, bizarre question, but it's a vague, bizarre problem. I'm just hoping this just jumps out at somebody that has seen this before.

Thanks
 
(This is Access 2003. )
Strange-ASCII-2.jpg
Strange-ASCII-3.jpg
Mark LaGrangeAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

bfuchsCommented:
I have seen similar output when sending long strings as parameter from Access to SQL Server.
My only solution was to save that string to a table and have my stored proc take it from there..
Jeffrey CoachmanMIS LiasonCommented:
Also make *sure* that your string does not have any "non-printable characters".

Also try formatting the string in "sections" then verify each section, ...then concatenate them together.
For example, ...format a string with all the text up to the email, and see if it displays OK.
Then in another string, ...format just the email, ...and see if that displays OK.
If the both display properly, ...then concatenate them together and see how that looks...

You also did not post the code you are using to create these strings, ...so we can investigate...

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Mark LaGrangeAuthor Commented:
I tried several things to figure out what was causing this; always the same element on the same records (the plan consultant e-mail address), but that same element concatenated fine on other records. I'll return to this later, maybe; too much end-of-year production work going on right now.

Thanks for your responses. Sorry it took so long to close the question.
Jeffrey CoachmanMIS LiasonCommented:
OK, great
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.