Re: Why not use VA/RPG

boothm@earth.Goddard.edu wrote:

>I had trouble with a couple of concepts though. One
>was the idea of the event-driven program model.

I've worked with event driven languages in the past, so this is not
new to me.

>Here's what I learned real quick though. Do inquiry-only applications
>at first, or at most, simple data gathering programs. It is real easy
>to update/delete a lot of records in a real hurry. (How I come to know
>that is not a funny story.) Plus, the real impact in my experience >is for the 
>inquiry-type stuff anyway, for non-data entry staff.

Is there something in the language that caused this? I don't understand
your warning.

>The other thing I learned is why client/server hasn't taken over the
>world. You really need to put a version number & date on every single
>thing you do. It is a pain in the butt.

Not sure I really understand. Why wouldn't you just put some kind of
current version checker in the program (load current version in a
dataarea on the AS/400 and check against a constant in the program). I
can't see where you would want to have older versions being used. Just
like you wouldn't want multiple versions of the same program running
on the AS/400. You would force them to download the current version.
This would be easy to do using a browser and FTP.

>By the way, Meyers & Sutherland's book is a couple of years old.
>There's a whole boatload of additional stuff you'll love available now.

I'll have to look for this info on a web site. Thanks for tip.

Joe Teff
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---