Shark Tank: Yep, that would explain it
<<   May/2007   >>
Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30 31  

Arts
Movies
Humor
Television
Music

Business
Internet
Finance
Jobs
Investing
Economy

Computers
Software
Hardware
World
Mobile

Games
Video Games
RPGs

Health
Fitness
Medicine
Alternative

Home
Consumers
Cooking

Recreation
Travel
Food
Outdoors

Reference
Psychology
Science
Education

Regional
US
Canada
Europe

Science
NSF
Space
Technology

Society
People
Religion

Sports
Baseball
Soccer
Basketball
 
29/May/2007 8:28AM
Shark Tank: Yep, that would explain it

A client/server application lets this organization's inside salespeople place customer orders at the prices quoted by the sales reps on the street. But something's not quite right, reports a pilot fish in the know.

"Back in November, we started having problems with a particular division," fish says. "Every morning, every order in the division's order log would delete."

And there's no obvious reason why. Various fixes don't solve the problem. The programmers say the code is fine. New application management settings don't clear it up. Adjusting how long orders are saved has no effect.

Then in April, the problem spontaneously clears up. Orders stop disappearing, and everything is OK.

For a week -- and then, without warning, the problem starts up again.

The tech who has spent months investigating the problem notices that one particular user always seems to be logged in just before the orders disappear. Maybe he knows something, tech thinks.

So he calls him. When you logged on this morning, did you notice if the order log was empty? tech asks.

"No, it was full," user replies. "That's why I delete all those orders."

What? asks tech.

"I clear out the order log on my computer as soon as I log on," says user. "It's really hard to see today's orders if yesterday's orders are in there, too."

You're deleting everyone's orders, stunned tech says.

"No, just on my computer."

No, that's shared data, sputters tech. When you delete them, everyone loses those orders. And if you do this every day, why did you stop for a week in April?

"Oh, I was on vacation."

Submit your own true tales of IT life to sharky@computerworld.com. If Sharky uses it, you'll snag a snazzy Shark Tank shirt! You can also add comments by using the form at the bottom of this page.

See more Shark Tank stories at the Sharkives.

Join Shark Bait

Now you can post your own stories of IT ridiculousness. Join Shark Bait today and vent your IT frustrations to people who've been there.
Go to the
Shark Bait homepage
or
Post a story now




Recent news in category
Nigerian flip-flop: Linux or Windows for schools? (and Grant vs. Google)
Whole Foods Market locks stable door after horse bolts (and woofski!)
Teaching an old dog a new trick

Global recent news
Laptop Buying Tips, Part 3
Strong Future for Video Conferencing
Microsoft's New Xbox Experience

29/May/2007 8:28AM
A client/server application lets this organization's inside salespeople place customer orders at the prices quoted by the sales reps on the street. But something's not quite right, reports a pilot fish in the know.&quot;Back in November, we started having problems with a particular division,&quot; fish says. &quot;Every morning, every order in the division's order log would delete.&quot;

25/May/2007 8:39AM
It's years ago, and this pilot fish is a developer working for a small company. &quot;Staff consisted of a few programmers, an office manager, a tech secretary and a part-time bookkeeper who's also the office manager's live-in boyfriend,&quot; says fish.&quot;Things were going as smoothly as could be expected until the boss left on an extended overseas trip.&quot;

25/May/2007 8:39AM
It's years ago, and this pilot fish is a developer working for a small company. &quot;Staff consisted of a few programmers, an office manager, a tech secretary and a part-time bookkeeper who's also the office manager's live-in boyfriend,&quot; says fish.&quot;Things were going as smoothly as could be expected until the boss left on an extended overseas trip.&quot;

25/May/2007 8:39AM
It's years ago, and this pilot fish is a developer working for a small company. &quot;Staff consisted of a few programmers, an office manager, a tech secretary and a part-time bookkeeper who's also the office manager's live-in boyfriend,&quot; says fish.&quot;Things were going as smoothly as could be expected until the boss left on an extended overseas trip.&quot;

24/May/2007 5:17AM
Jingle-jangle, Thursday's IT Blogwatch: in which Nortel digs itself a classic PR disaster. Not to mention the neuroscience professor who liked his email app's BCC feature a little too much...L'inq's Nick Farrell reports:Nortel threw its toys out of the pram after a former subsidiary, Blade Network Technologies, bought an Open Source Voice-over-IP from Fonality instead of using the telco's own PBX. Nortel probably would not have noticed the change but Fonality had a word with a blogger about why it made the move.Then, according to the VoIP &amp; Gadgets blog, a Nortel [executive] saw the article and 'flipped out'. He rang Blade, told it to return the Fonality system and demand that Fonality print a retraction to the blog article.

Copyright © 2006 Rootio Ltd. All rights reserved.