|
By the way I solved the positional problem using a piece of code that Buck Calabro kindly provided. It extracts the fields list from the ds and give back an array with the fields name. A lookup can get the position. If somebody want the source just contact me offline. HTH Marco --- Vernon Hamberg <vhamberg@xxxxxxxxxxx> wrote: > True, but if you need to test the column for NULL after you have fetched > (not in a WHERE clause), you have to have that NULL indicator variable. > One > problem Marco pointed out is, the NULL indicator array has to be resized > if > you change the number of columns. I don't know that this is specifically > an > RPG limitation when working with SQL, I also saw it in an SQL Server > context. I think it is a general SQL issue. > > We can also use IS NULL or IS NOT NULL in a WHERE clause but not anywhere > else I know of. > > Vern ______________________________________________________ Click here to donate to the Hurricane Katrina relief effort. http://store.yahoo.com/redcross-donate3/
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.