Re: Why NOT the web? -- MIDRANGE-L

Was a gui interface with current code not an option?
I would suggest a "stress" test of one completed .net application,
compared to the time existing app takes. 10-20 users banging away,
heads down order entry. They may find the point, click, enter, point again
entry screens take far longer to execute. Don't wait till whole project done
to
discover this. Single user demo/tests are worthless. You need to simulate
real life, very early in the development phase. I have existing web order
entry programs
that are not simple, and it can be done, but it takes a lot of thought
before coding.
jim

----- Original Message ----- 
From: "Booth Martin" <booth@xxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, December 29, 2004 5:59 PM
Subject: Re: Why NOT the web?


The Microsoft adage is "Embrace, Extend, Exterminate".

Don't underestimate .NET.  It is, and will be, good enough for many
applications, including the ones you mention.  Once embedded as the solution
for the client then the rest of the stuff that won't work becomes unneeded
and irrelevant.

Good luck.

---------------------------------
Booth Martin
http://www.martinvt.com
---------------------------------
-------Original Message-------

From: Midrange Systems Technical Discussion
Date: 12/29/04 16:45:36
To: Midrange Systems Technical Discussion
Subject: Why NOT the web?

I have a customer that wants to re-develop their entire "ERP" solution
using .NET.  The  stuff they have rewritten already, for instance,
will replace my RPG Pick Ticket Entry.  Pick Ticket is really nothing
more than an order.  Header/detail transactional stuff.

Most of the pick tickets come in through EDI and other methods, but
nearly all of them are reviewed on screen and manifested for delivery.

There are other procedures, like manual carton reallocation, Wave
picks, etc, that are all in RPG SFL's, and some C/S using windows
Visual screens, which they like very much.  My RPG stuff prints
100,000+ labels a day.  IT's lots of records, lots of database
searches, lots of EDI's, etc.

Actually, when I say web, I mean browser based.  They will use IE.

I've told them that the web is not for this kind of stuff, it's for
customer service, inquiries, simple ordering, etc.

They've asked me to tell them why.

So, even though I KNOW it's wrong to go that way, I can't think of how
to make my point.  How would YOU tell them?

I'm hoping Joe Pluta is listening.  This one is right up his alley.

The customer in question used to be a big one for me, but lately, not.
  I guess it's because they are moving to .NET, but that's no skin off
my nose.  I'll stay busier for the long run because the .NET thing
will never work.

This to me is a classic example of, let's get off the 400 and go to
..NET because it's on TV.  It's got to be good.

BTW, the examples I've seen have no capabilty for search screens, like
customer name,  terms codes, etc.  The Indian Liason says that's not
possible on the web.  My reply to my customer was, isn't that enough
proof that the web isn't good for this stuff, but apparently it isn't.

I've written some very nice inquiry stuff using Lansa for the Web, and
I have nice search screens :-)

Something strange is going on at this company, because everyone they
show the project to says it's awful and not close to completion,
except for the main guy who green lighted it in the first place.

The execs think that people like me will just tell them it's awful
because I will lose my job, but that's not how I work.  They think the
employees in IT that are going to be outsourced are trying to save
their jobs.  They've just given the Indian another payment so he can
continue.  I think someone is on the take, but that's another story.

I guess really I'm asking for my own knowledge, since I don't hope to
convince anyone at this future out of business company (FOOBCO).

Thanks.

--
Art Tostaine (GMAIL)
CCA, Inc.
Jackson, NJ 08527
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.




--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.298 / Virus Database: 265.6.6 - Release Date: 12/28/2004

.


----------------------------------------------------------------------------
----


No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.298 / Virus Database: 265.6.6 - Release Date: 12/28/2004



----------------------------------------------------------------------------
----


> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>