MS Office breaks interoperability betweem different versions, so it can go off the cliff.
I don't use GMaps, but for driving Waze with traffic warnings just can't be beaten. Hiking with OSM is great.
If I had a dollar for every time waze tried to save me time by taking a side street to avoid a light only to have me try to turn left without a light onto a major street at 7am in Los Angeles I wouldn't want to kill those devs.
I don't get your first statement at all. I have no problem opening anything in office 365 and I'm the only one in my office with 365, everyone else has a version of office suite that you could buy outright (which is my biggest complaint about 365, personally I'd rather own it) and we have 0 issue transferring documents back and forth.
Including our insanely complex payroll excel sheet that should be a database. We pay people on 7 different pay schemes, from hourly, to commission, to peice rate, with base rates and bonuses, to special pay programs, using insanely complex macros and external sources, most of which are Google sheets. And that workbook functions from 365 to 2003
I always get warnings that I can break, but it never actually does
What are you doing in office that causes it to break between versions?
My sister-in-law sent her bachelor thesis, edited in i-dont-know-which version, but in 365 was utterly misaligned. It was barely ok in 2007. It took some trial and error to see it in the same way she was.
Weird. We pass word documents back and forth all day and formatting is no problem. Even Adobe pdf to year conversions come out fine across the board.
I was just as suprised, as I was expecting it to work flawlessly on Windows Word, regardless of the version.
In any case, I will use sqlite before opening Excel. But usually Postgres.
MS Office breaks interoperability betweem different versions, so it can go off the cliff.
I don't use GMaps, but for driving Waze with traffic warnings just can't be beaten. Hiking with OSM is great.
If I had a dollar for every time waze tried to save me time by taking a side street to avoid a light only to have me try to turn left without a light onto a major street at 7am in Los Angeles I wouldn't want to kill those devs.
I don't get your first statement at all. I have no problem opening anything in office 365 and I'm the only one in my office with 365, everyone else has a version of office suite that you could buy outright (which is my biggest complaint about 365, personally I'd rather own it) and we have 0 issue transferring documents back and forth.
Including our insanely complex payroll excel sheet that should be a database. We pay people on 7 different pay schemes, from hourly, to commission, to peice rate, with base rates and bonuses, to special pay programs, using insanely complex macros and external sources, most of which are Google sheets. And that workbook functions from 365 to 2003
I always get warnings that I can break, but it never actually does
What are you doing in office that causes it to break between versions?
My sister-in-law sent her bachelor thesis, edited in i-dont-know-which version, but in 365 was utterly misaligned. It was barely ok in 2007. It took some trial and error to see it in the same way she was.
Weird. We pass word documents back and forth all day and formatting is no problem. Even Adobe pdf to year conversions come out fine across the board.
I was just as suprised, as I was expecting it to work flawlessly on Windows Word, regardless of the version.
In any case, I will use sqlite before opening Excel. But usually Postgres.
Fair enough.
The