Comment on Real Struggle 😔

• Zorque@lemmy.world ⁨5⁩ ⁨days⁩ ago

  Considering it is being saved in another format, I’d hardly consider this an excel problem.

  CSV has existed since before personal computers, much less Microsoft office.

  source

  • Dave@lemmy.nz ⁨5⁩ ⁨days⁩ ago

    Maybe, by why wouldn’t Excel let uou increase the number of digits in a CSV? The data is currently in Excel, and more digits isn’t incompatible with the CSV format.

    source

    • Zorque@lemmy.world ⁨5⁩ ⁨days⁩ ago

      Because it’s basically a text file. The data doesn’t exist anymore once you open it as a CSV on another computer. It’d basically just add zeros to the end.

      They could probably get that info from the other file, but that would mean getting that person to give it to you again.

      source

      • Dave@lemmy.nz ⁨5⁩ ⁨days⁩ ago

        Yeah thanks, I didn’t understand the original problem but I’ve got it now 🙂

        source
    • Fuck_u_spez_@sh.itjust.works ⁨5⁩ ⁨days⁩ ago

      You can’t increase the decimal precision beyond the limits of the available data which I think is what OP’s coworker wasn’t understanding – unless I’m the one who misunderstood.

      The coworker rounded the numerical data during the conversion from xlsx to csv meaning there was less data in the exported csv than in the original Excel file. They seemed to think the data did still exist in the csv but it was being hidden and that they could simply change the precision to unhide it.

      source

      • Dave@lemmy.nz ⁨5⁩ ⁨days⁩ ago

        Ahhh, the excel format keeps the precision but changes the display to 1 decimal. When exported to CSV, only that 1 decimal is exported, so you can’t bring back what isn’t there. But the original file still has it.

        I understand now, thanks! Definitely a coworker problem not an Excel problem then.

        source

        • -> View More Comments