The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
My daughter manages a college bookstore. Their parent company passes around a lot of Excel spreadsheets, and there's apparently a cottage industry in Excel macros among the manager community for reports, conversions, etc. She'd like to customize some of them for her own use.
Stop laughing, dammit, this is my kid here - this is serious!
Can anyone recommend a good book or two on Excel macro programming? There's a crap-ton of them out there.
And yes, I don't miss the irony of the request coming from the manager of a bookstore.
Excel VBA For Dummies, Walkenbach ... although it does seem rated by other readers
Professional Excel Development, various authors, Addison-Wesley
A guide to the wise ... if the macros have been recorded tell her to start by getting rid of all the unecessary waffle ... all the properties of a cell for example are not required to just change the forecolour.
And anything that says .Select or .Paste needs ripping apart
I'll be in the 60s. I don't expect to be dead so soon, and I suppose I will still be in active (retirement in my generation is going to be a bit more difficult)
About the preparation... I am going to investigate a bit and if I start something from the scratch, then I'll try to avoid it.
In Legacy mode... I think I will wait to see if it is really such a bad thing.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
One of the more fascinating bits of bilge I've found in my current job is that one of our subsystems uses Unix-style date/time handling, except that they chose January 1, 1980 as the epoch . Every time I have to with an ing date from this stupid thing I have to convert.
The Network Time Protocol has a related overflow issue, which manifests itself in 2036, rather than 2038. The 64-bit timestamps used by NTP consist of a 32-bit part for seconds and a 32-bit part for fractional second, giving NTP a time scale that rolls over every 232 seconds (136 years) and a theoretical resolution of 2−32 seconds (233 picoseconds). NTP uses an epoch of 1 January 1900. The first rollover occurs in 2036, prior to the UNIX year 2038 problem.
In Word you can only store 2 bytes. That is why I use Writer.