Comment on Real Struggle 😔

ZoteTheMighty@lemmy.zip ⁨1⁩ ⁨month⁩ ago

• DarrinBrunner@lemmy.world ⁨1⁩ ⁨month⁩ ago

  I managed to come up with a clever and innovative solution to the problem though; I gave up and worked on something else.

  There ya go.

  source

  • diabetic_porcupine@lemmy.world ⁨1⁩ ⁨month⁩ ago

    Yeah sucks when he’s the only guy giving you tasks and what else are you going to do?

    source
• panda_abyss@lemmy.ca ⁨1⁩ ⁨month⁩ ago

  Excel is pretty awful software. 

  10-15 years ago it was good, but it just isn’t anymore. 

  source

  • Zorque@lemmy.world ⁨1⁩ ⁨month⁩ 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 ⁨1⁩ ⁨month⁩ 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 ⁨1⁩ ⁨month⁩ 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

        • -> View More Comments
      • Fuck_u_spez_@sh.itjust.works ⁨1⁩ ⁨month⁩ 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

        • -> View More Comments
• jaybone@lemmy.zip ⁨1⁩ ⁨month⁩ ago

  That’s actually pretty terrible. Can you load the csv and then save it again as an xls? Once it’s loaded, why does it care what the source format was?

  source

  • Viceversa@lemmy.world ⁨1⁩ ⁨month⁩ ago

    I think you misunderstood the problem.

    source

    • Zorque@lemmy.world ⁨1⁩ ⁨month⁩ ago

      Is the problem that someone else is wrong and we want to relish in the agony of dealing with it?

      source
  • Resonosity@lemmy.dbzer0.com ⁨1⁩ ⁨month⁩ ago

    As soon as you convert from an .XLS file to a .CSV file, the data and sig figs used to display that data are saved while the math formulas used to calculate that data are erased.

    This means that when you try to go from .CSV to .XLS, Excel doesn’t know the original formula that created the data to then be able to display more decimal points. The formula is absolutely necessary to change sig figs of displayed data.

    The only other way I can think of that would allow one to change sig figs in .CSV data is if the .XLS file was converted with like the maximum number of sig figs displayed, or let’s say 10-20. Then in a .CSV, you can modify the sig figs to something less, like 0-20.

    But I want to say that if you save that file, where you original converted it with 10-20 sig figs but then changed them to 0-20, the .CSV overwrites the data and you lose the sig figs that you concatenated.

    source