How do I allow nulls in dbdef?

 5 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
Vito Amatulli
Advanced Member
Posts: 33
Advanced Member

    Does anyone know how to allow nulls using the dbdef utility?  I tried to contact Lawson but they told me since it was a custom table that I would need Professional services. I think that I may have to use the bldibmddl command to generate the SQL and then alter it to allow nulls.  If I use the bldibmddl command, will it allow that change to be recoginized by Lawson?  Any suggestions wouild be appreciated.

    John Henley
    Posts: 3353
      You can't.
      Thanks for using the LawsonGuru.com forums!
      John
      Vito Amatulli
      Advanced Member
      Posts: 33
      Advanced Member

        John,

        I guess I'm stuck using the bldibmddl statement and then managing any changes to the table. If I'm wrong, pleas let me know. I guess Lawson doesn't want any null values in their tables.

        John Henley
        Posts: 3353
          What is it you're trying to do? Read the data into Lawson, update it from Lawson, etc. ?
          Thanks for using the LawsonGuru.com forums!
          John
          Vito Amatulli
          Advanced Member
          Posts: 33
          Advanced Member

            We have a new interface that is coming in from a third party vendorr and my java developer does not want to have to update each field unless he has; hence the request to allow nulls. We created this custom table under out custom system code so it has been isolated away from the rest of the Lawson tables. I was just looking for a easy way to define nulls into the tables without using the Db2 tools set. I guess Lawson does not give us that option.

            Roger French
            Veteran Member
            Posts: 549
            Veteran Member
              Unless I'm missing something here, you can't have null values in primary key fields (or even secondary key fields) of Lawson tables. This is a common database design feature option.
              In other non-key fields, yes I would say it's entirely OK to have null values. Look at your EMPLOYEE table for example. Don't you see the COMPANY and EMPLOYEE fields as keys and that they are not null in dbdef and even in your database tools? Then check other fields, such as user fields. Notice some blank or null values?
              Posted By Vito Amatulli on 04/06/2009 04:09 PM

              We have a new interface that is coming in from a third party vendorr and my java developer does not want to have to update each field unless he has; hence the request to allow nulls. We created this custom table under out custom system code so it has been isolated away from the rest of the Lawson tables. I was just looking for a easy way to define nulls into the tables without using the Db2 tools set. I guess Lawson does not give us that option.