Re: need for simple web screen

Stored procedure is an SQL something defined on the IBM i - it can return a result set - we've had that for probably 15 years, even.

They are a way to hide and manage underlying data design and actual data. And you keep people out of directly hitting live data.

Those doing .Net to do a web site will be using ODBC or OLEDB to retrieve data - they can use direct access or stored procedures.

I think these terms are exactly what you have always thought they are - they are ubiquitous in the database side of our industry.

HTH
Vern

On 5/5/2014 4:15 PM, Booth Martin wrote:

uh oh. I believe I am about to learn something important.

Stored procedure? Result sets? My bet is that those terms do not mean what I thought they meant.

Is there a simple example somewhere that we can look at? Simple. Something that demonstrates the process to which you are pointing? Did I mention simple? (If you have ever looked at the examples on my web site you realize I like simple and overly obvious examples.)


On 5/5/2014 3:22 PM, Buck Calabro wrote:

On 2014-05-05, at 9:41 AM, Hoteltravelfundotcom <hoteltravelfun@xxxxxxxxx> wrote:

What are some methods to do a simple web screen it could be on a company
server.

It would show the actual shipments that have gone out till that point in
time.

it would get this data from one table on the ibm i, already summarized.
so we would show something like

Order type Total shipments
ABC 100
DEF 200

etc.

Before we can discuss whether we want a jacuzzi or a walk-in shower, we
need to talk about the plumbing. The first question you need to answer
is this: What is your intended web server? Is it a Windows server, a
Linux server or the i? Who controls the configuration of that server?
Do you have a way you can deploy your web application by yourself, or
will you need to involve a formal change management person?

The reason these questions are interesting is simple: If your company
has an existing web programming group who handle even your intranet
needs, then you might be facing an uphill struggle to be the newbie
amateur trying to deploy a .NET application to a production server.
Might. If your company forces all the web development to go through the
web people then your job will probably be to create some stored
procedures for them to consume. They love result sets. (Seriously.)

If your company hasn't got an established policy for intranet
development and you are forging the path, you have many avenues open to
you. I myself like to do it all on the i side because I control the
configuration, I control the deployment, I control the access and I can
debug each and every one of those parts from my desk. I'd still write
stored procedures to isolate the DB layer from the UI layer. You'll
love result sets. (Seriously.)

If you're a better .NET programmer than I am, and you have reasonably
free access to a Windows web server (do they still call it IIS?) then by
all means do it that way. Write .NET that runs on the server and have
it call stored procedures that you write on the i side.
--buck