@matigo I'm surprised there aren't strict, anti-USB-stick policies. We've made it so easy to abscond with sensitive data now.
@matigo Mostly minor fixes and feature additions in modules other than payables. The usual stuff that happens as we all plod forward. The big problem is newer versions of Windows being tossed into the mix,
@matigo You mean, "When I die". I'll never retire. Also, I have some other people in the wings being trained for that eventuality. ;)
@joeo10 With our software, it isn't that big of a deal if they are only using the payables module. Only becomes an issue when they start adding new equipment to the mix. They have a mixture of Windows 2000, XP and RHEL 5.
I used to get onto people about it but it does no good. I just wait until things go haywire and they call.
@matigo Stories like this are why I am so thrilled to no longer have to answer to anyone.
@matigo A version where we never completed client dialog to map Windows dot matrix shares to our internal drivers. Had to remember the schema and add the mapping in the database myself.
It's after 5:00PM, Tom. Why have you not left the office yet?
Well, a customer called wanting to get a Windows 10 computer printing to a dot matrix printer shared by a Windows 2000 machine. Impossible. 10 simply would not allow it. I had to log onto an ancient RHEL5 server, map the windows 2000 share, enable samba, configure max_protocol to NT1 so Windows 10 could talk to it and have the Windows 10 machine hit THAT share.
Also, they are 102 releases behind on their software so I get to address that at a later date.
Ugh.
@peemee I want the Air's ports and the Pro's display. Unfortunately, I cannot have that :(
// @matigo