Discussions
Categories
- 197K All Categories
- 2.5K Data
- 546 Big Data Appliance
- 1.9K Data Science
- 450.8K Databases
- 221.9K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 552 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 556 SQLcl
- 4K SQL Developer Data Modeler
- 187.2K SQL & PL/SQL
- 21.4K SQL Developer
- 296.4K Development
- 17 Developer Projects
- 139 Programming Languages
- 293.1K Development Tools
- 110 DevOps
- 3.1K QA/Testing
- 646.1K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 161 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 19 Java Essentials
- 162 Java 8 Questions
- 86K Java Programming
- 81 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 205 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 474 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 175 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 233 Portuguese
Poi compound file
Dear community,
The first 16 bytes of every 4096 byte are not displayed correctly at office products for windows. They 16 bytes are completely randomly displayed:
Example :
7c bc 51 db bb 0b 8b 26 16 cc 04 f6 62 59 39 87
instead of:
78 63 65 70 74 69 6f 6e 20 4c 6f 63 6b 65 64 3d
Has anyone of you an idea why this could be possible?
I would be very happy for help!
Thanks all
Best Answer
-
Wrong forum!
This forum is ONLY for Java questions.
Please mark the thread ANSWERED and repost it on a forum for Microsoft products.
Answers
-
Wrong forum!
This forum is ONLY for Java questions.
Please mark the thread ANSWERED and repost it on a forum for Microsoft products.
-
Acutually, it was a java question. I created the office file with poi (JAVA) and wanted to check if the displaying error was a bug of the compound file. However, I marked it as correct, because it does not look like an issue of the compound file itself.