- Feature Articles
- CodeSOD
- Error'd
- Forums
-
Other Articles
- Random Article
- Other Series
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
Yeah. Sometimes, though, they have no choice but to (re-)key the data in. Take my wife's former employer (a taxi company). First she got all of the corporate vouchers, half filled in by taxi drivers (whose handwriting is worse than doctors, as far as I can tell). Then she had to cross-reference the trips in the dispatch system. Then, because the purveyors of said system had disabled copy/paste during one of their upgrades, she had to key all of that information into Quickbooks (or Excel, depending on which cantankerous client the bill was going to). Of course, then she had to staple them to sheets of paper and Xerox them because the people being billed would refuse to pay unless they saw a copy of the voucher (and sometimes refused anyway).
That's thousands of vouchers per month.
All with the worst handwriting you've ever seen.
Being paid to work hourly, but no overtime because the owner was morally opposed to spending money. 50-60 hours a week.
I actually wrote her a Perl program to reformat her 30k-50k line Excel spreadsheet and create the formulas. Saved her 8 hours a month. Owner never knew, and didn't care.
I'm glad she quit.
Admin
There is a simple solution to apps like this - don't support them.
I worked in a job where the policy was "if you build it or another staff member builds it, then you are responsible for what goes wrong with it". This policy arose as result of situations similar to the one described. It forced critical apps to come out of the woodwork and be re-developed if necessary and cut down on pesky service desk inquiries.
MS Office 'extensibility' is responsible for so many problems its a wonder someone hasn't tried to sue them!
Admin
Wi nøt trei a høliday in Sweden this yer? See the løveli lakes The wønderful telephøne system And mäni interesting furry animals
Admin
Sorry, meant to quote. was simply too funny...
Wi nøt trei a høliday in Sweden this yer? See the løveli lakes The wønderful telephøne system And mäni interesting furry animals
Admin
Use action verb?
Admin
I've just put a price on N Morrison's head.
Admin
Admin
Ok! Cool, thanks. Pretty sure Excel won't be used in 2100 anymore, though. (At least I hope so.)
saepius
Admin
I'll betcha $100 it's still in use in 2100. Consider: Kodak, made up name in use almost 100 years later. Ditto Rolex. This assumes we don't run out of power or off ouselves first.
Admin
He'll probably end up doing himself just to claim the reward.
Admin
Then how do you spell wøøsh?
Admin
Møøse trained to mix concrete and sign complicated insurance forms by: JURGEN WIGG
Admin
When I hear the word "Excel", I reach for my pistol
Admin
In one you get the same amount each week which is based on 40 hours times your base salary. In the other you get the same amount each week which was initially based on what would have been your hourly rate times 40. Unless you mean the owner promised overtime but then didn't pay it. In which case after about week 2 you either quit or sue.
Also, why the hell would the owner care that she's using a little perl program. Was he also opposed to a free way to do things faster?
Admin
However given the exponential growth of computer it's almost unfathomable that Excel as we know it will be around in 90 years. Perhaps Microsoft (or whoever they've morphed into at that point) will still have a program called Excel, but I very much doubt that it will even remotely resemble our current Excel.
Admin
"N Morrison is a VBA programmer."
Wrong again. Algol 68. Has anyone seen my Burroughs B6700?
Admin
Yeah, I was just thinking the words themselves. I read recently that Rolex, the name alone, is worth 3 billion dollars.
I see Excel as a software implementation of an accountant's tablet. Sure, there are a zillion bells and whistles, but what you see first is recognizable and usable rows and columns. Cuniform tablets, accountants pads, data tables: rows and columns. We won't cast off that metaphor anytime soon. When the power runs out we'll go back to the accountant's tablet and long for the days when we had Excel.
But cell Z24 is a travesty.
Admin
Was this software developed in India?
Admin
That sort of reminds me about how we don't know what the programming language scientists will be using in 2100 will look like, but we're pretty sure it will be called Fortran.
Admin
What they'll hear is "You have to flurb the wootle", and you damn well know that. That doesn't come close to solving their problem.
Admin
"c'mon, don't be unhelpful" is just a polite way to say "you suck as an electronics engineer." And they are damn right.
Admin
Admin
Congratulations, and thank-you for sharing.
Admin
Oh My, Oh My....Two of you incredibly smart people that can work out how to use MS products.
The rest of us are positively green with envy
Admin
Can't you...???
Admin
She was trying to access the FlightSim that appeared in some versions of Excel....I think she edited the wrong cell.
Admin
I once had the gaul to suggest replacing a horrendously complicated spreadsheet with a real program. As the Financial Research assistance where constantly having trouble with it anyway. The response was. If you do so the software will become your sole responsibility and the research department will refuse to take any further care of it. Update the various parameter lists and weightings. My argument that I could furnish the system with very simple configuration files that where easy to update fell on death ears.
Admin
uxor==husband
Admin
and when they refused, you shrugged?
Admin
Admin
Admin
Admin
Admin
What? Not zoink the spiffler? You sure?
:-P
Admin
From FLSA:
So, if a degree means you're likely to be exempt, is that why HR always wants IT to have a degree?
It also specifically says Accountants are exempt from FLSA rights, as in they have no rights from the FLSA. What rights they have from other acts or statutes, I don't know.
I'd also like to add that it depends on the state as well. In California, the laws are much stricter on businesses: More than 8 hours in a day is overtime, more than 40 hours a week is overtime, more than 8 hours on your seventh day of the week is double time.
Admin
I reckon you were dealing with what most companies would call Analysts. We're the happy bunch of people who sit within Finance, but translate data into meaningful information (and occasionally vice versa). You get the Sales and Marketing people who need help converting data into helpful information for their account set, the Accountants who want a nice easy way to avoid re-doing all their calculations when the Cost Of Goods change, and you also have the IT people who are too remote from the business and need the business requirements explaining, like taking the main data warehouse down during the financial month end is not a good idea.
Admin
How do you do that? No kidding, I can't find the button!
Admin
Is that you Yoda?
Admin
Admin
In a previous life, I had to maintain a 1 megabyte Symphony spreadsheet (that was 20 years ago, so it required crying-edge 80386 computers with beaucoup ram) that had many such formulas.
To save time, I programmed a formula reformatter that nicely indented the parentheses.
Admin
Admin
pfftt! That formula's not so big. I used to maintain an application that calculated the performance of annuities. The calculations in the app had to match those in a spreadsheet for each annuity product (the duplication actually helped with verification). When the calcs didn't match, I would just take a very deep breath, get comfortable, and get mentally prepared for a very long session. I would end up tracing through dozens of cells each having formulas as long as that. If I suspected the problem was in the spreadsheet, I would have to explain the path through all the calcs back to the actuary.
Admin
This actually reminds me of some Access queries that I had to maintain.
The purpose was to assign a score based on a range. Like if the percentage was 0 the score was 100; percentage between .01 and .05, the score was 90, etc.
The queries had a series of nested IIF statements which did this. It was bad enough that they were hard to figure out by looking at them, but each year the formulae would change so they'd have to be modified. And the database had multiple scores that had to be calculated.
I wrote a function in code instead and just passed the percentage to it. Incredibly easy to maintain. No one had done it that way before because they didn't know VBA.
Admin
THIS!
Admin
In all likelihood, he got nothing out of it except for a few nice words. But you can bet that she'll be calling him up again every time her computer has a hiccup.
Note: debugging an Excel formula, even if it's a mile long, will NOT cause a woman to wet her panties.
Admin
Admin
Can't believe I took the time to format and actually understand that abomination of a "formula". Sad but true: large formulas in Excel have no way but to get ugly and confusing because you have no way to keep them understandable and structured.
Admin
Admin
do you really need a formula?
number of passengers = number of seats
;)
captcha: saepius = ewww
Admin
Why not ;-(