🚀 go-pugleaf

Not 100% sure about this, but I think you need to put a compiler option on
CRTBNDRPG or CRTRPGMOD to handle null-capable fields. (ALWNULL in the DDS
was correct.) Then, in the program, when you read a record with null-capable
fields (like your date field), I think the null-field map is in the INFDS
somewhere (I could be wrong). Anyway, what you would do then is to set the
NULL-switch for your date field on before you write the record.

I suppose it might be easier if you used embedded SQL. If that's an option
for you, you could set the field to NULL directly in the INSERT statement.

"ricko" <ricko@softlad.co.uk> wrote in message
news:3a87c97a$1@d2o313.teliauk.com...
> Hi
>
> I am trying to populate a Sequel Database with Data from an AS400 File
> (ODBC). The AS400 file
> contains several DATE Fields that have the field date property assigned.
> (L).
>
> I do not always need the dates to contain a date i.e. I need them to be
> Null. However, When I run
> my RPG Program to populate the AS400 file, the Date fields default to
> 1940/01/01 (*ISO Default).
>
> This is causing a problem because the Application that uses the Sequel
> database displays these dates
> to the users and I need them to be Blank.
>
> The ALWNULL and DFT Keywords do nothing to help. I have changed the DDS to
> be a 6 char numeric
> field but then Sequel detects that its not a date field and rejects my
file
> transfer.
>
> I am trying to automate the entire process without and 'manual'
> intervention.
>
> Is there a solution??
>
> Thanks in Advance!
>
> Paul Cullen
>
>
>
>