Are you sure you used the correct formulas? I get this:
7249 cannot be the result of applying OCT2HEX to 7111...
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello,
I hope someone can help me with this.
I have a spreadsheet in which I have 6 sets of numbers, (total of 27 digits), 2 binary and 4 octal, which I all convert to hexadecimal value, and then combine into a 14 character string.
This string is meant to be used to make it easier to regenerate the original 6 sets of numbers without having to enter all 27 again, and the conversion to hexadecimal is to avoid making it too easy to see how the code is generated. So the workbook creates the string, but also allows to paste a string and break it up into the original 27 digits.
Creating the string was not a problem, but now when I have the 14 character string and break it up in the original 6 parts, converting it back to the binary or octal numbers gives errors or different results.
Example (first column original value, second column result after bin2hex or oct2hex, third column result after hex2bin or hex2oct
| 11111 (binary) | 1F | #VALUE |
|---|---|---|
| 141 (octal) | 61 | 141 |
| 444 (octal) | 124 | 444 |
| 113112 (octal) | 964A | #VALUE |
| 11111 (binary) | 1F | #VALUE |
| 71111 (octal) | 7249 | 71111 |
Inbetween these steps I use the CONCAT formula to make it into one 14 character string, and the LEFT and MID formulas to break these into separate sections again, where the hexadecimal values before and after are the same, so I would expect the same value in the left and the right column.
Does anyone have an idea where I'm going wrong with this?
Thanks.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Formula is correct, just missed a digit in the original OCT number, it's 71111.
I'll correct it in the table of my first post as well
I don't know why, but the problem was when I was trying it on my personal laptop during a day off from work with a Dutch version of Office. Now I have rebuilt it from scratch at work on an English Office version and it works without any problems, so this thread can be closed as resolved.