• Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

Spreadsheets

Having worked around this in the early stages of Covid in a different jurisdiction, I have a great deal of sympathy for anyone who decided on Excel with a password on a secure server to get off the ground. This was at the point when parts of Spain and Italy appeared to be on the point of meltdown.

It is the failure to migrate which should see P45s issued.


completely agree, the first month using sellotape & chewing gum was acceptable. As usual the techies were probably screaming and the managers were busily ignoring it.
 
I know why they have an exemption as above, now how long will that be acceptable if they spaff all the information to the publc?

But that's a breach regardless of the legal basis (including consent) for processing the data. I was just pointing out that consent is not required.
 
completely agree, the first month using sellotape & chewing gum was acceptable. As usual the techies were probably screaming and the managers were busily ignoring it.

Well, week one we had army cadets with pieces of paper. Excel was an upgrade. But it soon moved on from there.
 
hmm

How to Remove, Crack, or Break a Forgotten Excel XLS Password

I agree its probably part of the transfer process as well so whichever idiot designed that needs a P45. CSV/XML is the best for such things.

CSV is what they used. The labs send their data in CSV files to the central place, which then imports the CSV into Excel to produce the stats. However, the stats place had created their spreadsheet based on a .xls template rather than a .xlsx template, so it had the old limit on the number of rows and silently discarded the excess when the CSV file had too many rows. At least, that's what seems to have happened, as far as one can tell by trying to extract the signal from within the tremendous amount of noise surrounding it.

I suppose they could try to blame Microsoft for maintaining backwards compatibility in their products :rolleyes:
 
CSV is what they used. The labs send their data in CSV files to the central place, which then imports the CSV into Excel to produce the stats. However, the stats place had created their spreadsheet based on a .xls template rather than a .xlsx template, so it had the old limit on the number of rows and silently discarded the excess when the CSV file had too many rows. At least, that's what seems to have happened, as far as one can tell by trying to extract the signal from within the tremendous amount of noise surrounding it.

I suppose they could try to blame Microsoft for maintaining backwards compatibility in their products :rolleyes:


The cool kids use XML now :wink


what can I say about what they are doing? oh yes! :facepalm::facepalm::facepalm::facepalm::facepalm::facepalm::facepalm::facepalm::facepalm::facepalm::facepalm::facepalm::facepalm::facepalm::facepalm::facepalm::facepalm::facepalm::facepalm:
 
If any government interns are reading this, please get in touch as I can assure you that I can do this much better and almost certainly for less than you are paying AccentPwCTata for this.

Oh, and ignore Bob. His cheapness is not worth the spreadsheet he has typed it into.
 
I just learnt today - according to the Prime Minister - that a manual error isn't also an excel error.

Did the PM ever have a job?
 

Advertisers

Back
Top