This is a multi-part message in MIME format. ------=_NextPart_000_0006_01BEE8A1.CED50C00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Allrighty, this is what it took in case any of you see this: First > On the mainframe side I had to use QUIZ to generate the portable = file since it will allow me to format the date when it writes: REPORT SUMMARY COMMENT_DATE FORMAT YYYYMMDD Second > I had to change the format in Axiant from DATE to DATETIME, = making sure the change reflected both in the structure and database. The data loaded just fine, and when I pulled it up in a screen, it = displayed the date with the century as it should. The first clue came from Roger Marcinik who sent me some Oracle = documentation that says it stores the date information with the time = included as CCYYMMDDHHMMSS. Thank you all for your help, Walter ------=_NextPart_000_0006_01BEE8A1.CED50C00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">Allrighty, this is what it took in = case any of=20 you see this:First > On the mainframe side I = had to use=20 QUIZ to generate the portable file since it will allow me to format the = date=20 when it writes:REPORT SUMMARY COMMENT_DATE FORMAT = YYYYMMDDSecond > I had to change the format in Axiant = from DATE to=20 DATETIME, making sure the change reflected both in the structure and=20 database.The data loaded just fine, and when = I pulled it=20 up in a screen, it displayed the date with the century as it=20 should.The first clue came from Roger = Marcinik who sent=20 me some Oracle documentation that says it stores the date information = with the=20 time included as CCYYMMDDHHMMSS.Thank you all for your = help,Walter