Re: BLOB's on AS/400?

Mark,

For example might single report or inquiry that allows the user to select the 
fields 
printed/displayed, the order of the records, selection criteria, etc. is a lot 
less 
kludgy than locking the report/inquiry solution domain to what is known when 
the program is being developed.  I don't see why separating data selection and 
manipulation precludes dynamic access.
  
When you look at your applications, I think you will see that a lot more is 
similar 
about your applications than is different.  SQL is one tool that is very 
helpful when 
you build your applications using a framework of  components that support these 
similarities.  SQL isn't the only way to allow your applications to support 
dynamic 
data access, but it is the easiest.

David Morris


>>> mlazarus@ttec.com 05/03/00 08:44PM >>>
David,

At 5/3/00 10:30 AM -0600, you wrote:
>I agree that SQL and RPG need to work together.  I find that SQL helps to 
>eliminate
>kludgy RPG programs.

  How?  Can you give an example?


>It gives RPG dynamic access to data, which is a very powerful feature.

  I can think of a few cases where it would be handy, but, with the 
exception of connecting to another system, I would rather separate the 
selection of the data from the logic of data manipulation.

  -mark

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