|
Bruce, Good point, but the original question revolved around work fields, and using SQL for work variables is a bit messy, to say the least. All SQL variables are nullable, so writing an SQL-language stored procedure may be one way to approach this. Of course, if one wants to write an SQL-language stored procedure one needs to have the C compiler, DB2 Query manager and the SQL development kit installed... Sigh. Buck Calabro Aptis; Albany, NY mailto:Buck.Calabro@aptissoftware.com > -----Original Message----- > From: R. Bruce Hoffman, Jr. > Sent: Tuesday, October 12, 1999 7:40 AM > To: RPG400-L@midrange.com > Subject: Re: Null Capable Fields > > Not a work around, a different way of working. > > Use embedded SQL statements for IO. This allows you to then accept the > null indicators in select statements. > > bellis@ORIENTAL.COM wrote: > -snip- > > > Is there a way to define fields internal to RPG programs as null > capable? > > If not, is there a work around for this? > > > > Thanks, > > Brian Ellis. > +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.