Program crashes with wireless

[Paul D. Elliott]

Sheesh. I must remember to not give background info in my replies as it
sometimes just stirs up things better left alone.

Well, just this last time ( maybe ). This program was used to track packages
received by the warehouse to be delivered to people around the company.
The system that it replaced was ancient and sort-of stopped working seeing
as how the company did not want to spend $4000 to $10000 to get the
updated program that worked with Windows ( this was a DOS version that
was no longer being maintained ). So I'm now on staff and getting paid and
had the spare time to do the job. It only took a couple weeks to get running
( amid doing support for the other systems which took priority ).
The wireless connection had been installed 5-7 years prior to this when
the needs of the warehouse to access the main intranet was very
minimal. The warehouse manager and my manager decided to not press
the issue.
If I could solve the problem in a couple hours work then that was much
preferred to involving 2 or 3 ( at least ) high-paid network techs for even an hour.
They got paid 2 or 3 times more per hour than I made.
The whole problem got "solved" last month when the company laid off
another 20% of its people and laid off all but 2 of the warehouse people
and out-sourced the main warehouse functions to another company.
Those 2 people were moved to a small room in the main building and hooked
up with the normal wired intranet. As a side note, I was laid off 4 years
ago in another of their re-orgs which laid off 20% of the company. The
program is still working fine today with the small exception that the IS
department hasn't figured out how to move the network printer to the
new area ( the program writes to the printer queue as no computer has a
printer attached locally ).

Sorry if that sounds like a rant. If many complain then I'll delete the post.

[Joe Byrne]

>I know precisely what I'm doing and don't cut corners

I hope you are not recommending this approach. It would simply destroy the entire belief system of the Generation X'ers now coming into poisitions of real power in the business world.

MCM

yea, I know, but I feel obligated to let them know that, despite what the media says, there are people who think differently than McHillary

[Michael Mattias]

>I know precisely what I'm doing and don't cut corners

I hope you are not recommending this approach. It would simply destroy the entire belief system of the Generation X'ers now coming into poisitions of real power in the business world.

MCM

[Joe Byrne]

And people wonder why I despise wireless

Hummm. I've been in the networking end of the business (my primary line of work, programming secondary) for over 20 years. I've installed a few hundred commercial grade wireless solutions over the last 8-10 of those years. Can't say that I've ever had a single bad experience that was directly related to wireless technology. But then again, I know precisely what I'm doing and don't cut corners

[Michael Mattias]

this application was not a money-making project for the company so very
little effort was expended by the IS department

If it required as much as one minute of any employee's time to "deal with it," yes it was, because there was a cost, therefore it 'made' negative dollars. (Unless all your employees are unpaid volunteers).

That cost BTW came right off the bottom line, meaning right out of your last raise.

MCM

[Arthur Gomide]

And check the presence of X-ray devices too!

[Don Schullian]

Thanks, all, I'll start looking down this track.

[Mel Bishop]

And people wonder why I despise wireless.

Anyway, ask him/her/them if there are any RF generating devices located nearby. Flourcents, radios, etc. Your description smacks of data being scrambled/corrupted.

[Cliff Nichols]

this application was not a money-making project for the company so very
little effort was expended by the IS department.

I bet if it was a "money-LOSING" project, the IT dept would invest more time into why or how to fix it.

I know I loosely state that because of the whole "Butting Heads of Dept's" where each dept thinks the problem is on the other departments end and not theirs.

Sometimes its worth pressing a point of a problem (especially if you have the data to back it up, know whats causing it or at least an idea of what is causing it, or at least logs showing the problem (hopefully a pattern) to track down the problem. Rather than "Work-Around" and forget it)

[Paul D. Elliott]

Yes, had the same problem. kept getting time-out errors ( don't remember
off-hand the err # ). ended up doing checks on every TRM call to retry
up to 3 times if I got the time-out error. my program was running in a warehouse
which was across the road from the main buildings and connected via a
wireless connection. The IS department was never able to eliminate the
problems ( even after 4 years of errors ). but retrying the TRM call did clear
up the problems as far as the users were concerned.
I kept logs of when it happened just for my own use as
this application was not a money-making project for the company so very
little effort was expended by the IS department.

[Don Schullian]

Hi,

Got a program that uses Tsunami to store the data. It has been running for a few years now but the client, recently, tried it across a wireless network and it failed. (Not sure but sounded like a GPF) No problems have been seen with a hard-wired network.

Any ideas?