Thanks. Actually, that's already my existing solution but, that doesn't work with "/", "-", & ":" present in the string.
Any idea?
d_york
works in English in C# .Net for all those strings - those are not metacharacters. I hate to say "normal" but this should work on a "normal" setup without issue. Something else is going on, you've got more going on than a simple set of pipe delimited lines of text. You'll probably have to divulge more information to get assistance from those more worldly than me. But if I were just handed this issue to debug in code I'd be looking at:
1) Encoding: If I'm reading delimited text from file am I really getting what I think I'm getting? I'd be looking at the language and the encoding being detected.
2) Operators: If I've got particular issues around the characters you mention I'd be thinking they are being treated as operators somewhere in the code. And what I'm getting isn't a "string" but an object like a DateTime or Double or something.
3) Dev Environment: I'd suspect the coder was maybe coding toward Mono on Linux or something and it's a compiler or other issue.
Based just on what you posted, I had zero issue splitting those lines of text and converting the third element to an Int. But I'm "seeing" plain text in English - I'm not seeing all the other factors that could be in play here.
JimiJ13
ASKER
d_york,
You are correct. I traced the issue on the Dot Net coding that concatenated the string thereby resulted to erroneous data extraction.
Thanks. Actually, that's already my existing solution but, that doesn't work with "/", "-", & ":" present in the string.
Any idea?