* Posts by SpottyOwl

2 posts • joined 23 May 2018

Developer’s code worked, but not in the right century

SpottyOwl

Re: Because computer dates are numbers but real dates aren't

I was involved in writing a few systems for the local NHS in the 1980s and 1990s, using Clipper. I bottled out and stored all dates as strings in the YYYYMMDD from the beginning and so had a slight overhead in some aspects of processing but indexing, grouping, etc. was easy.

I was asked to confirm in writing (and, for all I knew, sign my life and first-born away) that the system was Y2K compliant. I took the easy option, said that my software was, their hardware...maybe...other software involved...certainly not, and so I couldn't sign off.

As they say, I never worked in that town again. :-)

Ironically, through the early 2000s I got contacted by other NHS units that was using the software I'd written that I didn't know had it, and they had no problems. I must have got something right.

About to install the Windows 10 April 2018 Update? You might want to wait a little bit longer

SpottyOwl

It worked for me as well....

Sorry to say that the update process - and every other Windows 10 update I've done - worked fine.

This has been on a range of machines - 8 year old Dells, 6 month old SSD Fujitsus, Surface laptop, and a very ancient HP laptop.

Longest it took was about 45 minutes - machines running a variety of software including Office, SQL Server, Visual Studio, mySQL, etc. .

Biting the hand that feeds IT © 1998–2019