After install the snapshot version I had success in doing a browse in DB2 tables. There was new errors that I report below in the way people can try to fix them:

1. Any update in table(via INSERT, UPDATE or DELETE) generates a empty Message Dialog. I'm talking about an application developed with DBNavigator and DBGrid;

2. People that uses DB2 in mainframe applications has the habit of use TIMESTAMP fields as keys to make relation between tables. The format of TIMESTAMP that is returned isn't useful since it eliminates the 6 digit fractions of second. When you download the data from mainframe to DB2 tables in the low platform it's necessary to keep mainframe format compatibility because there are COBOL environments that emulate mainframe behavior. The idea of these cobol environments is test in the low platform and upload the sources, compile, catalog and run applications on mainframe without new tests. More over it must be thousands of other applications that would benefit of DB2 TIMESTAMP format. BTW, the format of TIMESTAMP in DB2 is YYYY-MM-DD HH.MM.SS.UUUUUU. IMHO, any other format seems to be not correct for DB2 approach.

My use of Lazarus with DB2 via ODBC will be restricted to browse functions without updates.

I hope I have give contributions to DB2 interface evolution.

_________________________________________________________________
    To unsubscribe: mail [EMAIL PROTECTED] with
               "unsubscribe" as the Subject
  archives at http://www.lazarus.freepascal.org/mailarchives

Reply via email to