RE: VARPG Question...

["Flagler, Rick" <flagler@xxxxxxxxxx>]

I've written HOST side programs that take the same approach as Booth
mentioned but it's probably harder to code in some respects. Would be nice
if VARPG handled embedded SQL just like HOST RPG.

Have you used VARPG when using SQL triggers and constraints on the Host? It
would seem that now you could build the business rules for fields and/or
table relationships with either NATIVE or SQL constraints. Then in the VARPG
application, you wouldn't have to deal with coding them but more with
reacting to the firing of a constraint that had been violated. Although the
"version" of RPG used for VARPG hasn't always kept-up with RPG on the
iSeries, I think everything is there to get the file-i/o messages that
result from a HOST DB2 constraint violation. Are there SAMPLES that depict
that? If not, perhaps there should be.

Rick Flagler
Manager, Information Technology Projects
Timken Super Precision (MPB)
Keene, NH 03431
(603) 352-0310


-----Original Message-----
From: Booth Martin [mailto:Booth@MartinVT.com]
Sent: Tuesday, February 19, 2002 7:42 PM
To: code400-l@midrange.com
Subject: Re: VARPG Question...


--
--
[ Picked text/plain from multipart/alternative ]
The connection is reasonably fast  -  faster than java and HTML solutions in
my experience.  The user training is way easier.

My experience was that VARPG has a steep but fast learning curve; at least
to reach that first "Hello World" program.

The applications are divided into "Application" and "Runtime".  So far I've
had more success by including the runtime in each application group.

Design is the major issue.  Data base design, business rules, and
enforcement have been issues I have found to be more difficult than building
VARPG to the design.  In self defense I've started building business rules
and maintenance into a single application that has *OWNER authority and
resides solely on the AS/400. No other application is allowed to
add/update/delete the actual data files.  Data and error messages are
sent/received through parms.



---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@MartinVT.com
---------------------------------------------------------

-------Original Message-------

From: code400-l@midrange.com
Date: Tuesday, February 19, 2002 15:20:40
To: CODE400-L (E-mail)
Subject: VARPG Question...

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Hi all,

Ok, I admit that I know less than nothing about VARPG, so this might be a
very stupid question. That's my disclaimer.

Anyway, I am working on developing a store returns management system to
handle customer returns. The database will reside on the AS/400. If
possible, I would like to have a GUI interface at the stores. Could VARPG
handle this at 170+ stores? Would I have to access the files through an ODBC
connection, or would it be as if I signed on to the 400? Also, what is the
performance of such an application? Or, is VARPG even designed for such an
app?

I'd appreciate any input you might have. (I'll also have to go through my
deleted emails and find the ones from last week where someone asked for
sample code)

Thanks,

Chris Proctor
Manager of Systems Integration
Gart Sports


1050 Hampden Ave.
Englewood, CO 80110

Phone (303) 863-2280
Fax (303) 863-2263
mailto: cproctor@gartsports.com

_______________________________________________
--
[ Content of type image/gif deleted ]
--

_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.


**********************************************************************
This message and any attachments are intended for the
individual or entity named above. If you are not the intended
recipient, please do not read, copy, use or disclose this
communication to others; also please notify the sender by
replying to this message, and then delete it from your system.

The Timken Company
**********************************************************************