Re: 'green screen' not sellable

IBM.Data.DB2.iseries or whatever the .net access library works very
well. You can connect to it transparently from .net just as you would
an ms sql server. It makes no significant difference to the .net
developer. You can store business logic in stored procdures or make
program and command calls as well. Access data queues, etc. The last
shop I was in was completely homogenous with green screen apps and .net
applications/services accessing rpg business logic.

You can even use entity framework I beleive but you might need db2connect.

The problem with i is the sales pitch. Instead of being sold as a green
screen system it should be sold as an amazingly featureful sql server,
business logic repository and reporting system that even has a proper
command line interface.

C# is the way to go for many many reasons.

Thanks,
Mark


On 06/08/2015 10:57 AM, Gary Thompson wrote:

Some years ago a co-worker used Delphi to give our warehouse an interface that allowed them to "move" customer orders
to a particular dock door for shipment. They also could change shipping dates and times using mouse and keyboard.
This replaced several printed reports and JD Edwards green screens and training time was shorter and accuracy improved.
It helped that my co-worker had a good sense of design, but the key was the windows form-based interface and good use
of color.
The .Net platform is also a good option and could have advantages.
Before I left that company we did a small C# project which went well.
I don't know enough to argue for/against either one.

For maximum flexibility, you may want a browser-based solution, but, to me, that's a bunch more work, but there are
newer/better tools in that space as well.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Hoteltravelfundotcom
Sent: Monday, June 08, 2015 8:36 AM
To: Midrange Systems Technical Discussion
Subject: 'green screen' not sellable

I was talking Friday with an owner of a company that has billing software for a particular industry.
Where there are frequent, government and insurance changes they have to apply.

Their software is based on RPG. He said they want to rewrite in C# because they cannot sell to new customers.
OK fair enough but do you think C# based is the way to go? Secondly he said that they will keep the data on the IBM I.

Actually I have been working with mobile apps lately connecting a desktop system using Delphi and I was thinking this might be a better way for them to get their product to the public relatively sooner. Taking a complicated old database from ibm I and trying to fit in C# I think it hard but what are their choices?
--
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.