So..... I got my DB2 project working to display and edit existing records.



When I try to add a record I always get a conversion error on the primekey field.



I know DB2 doesn't have auto increment fields (does it?) so I have to manually manage the primekeys but I don't even get a chance. I get this error as soon as I hit the add button, or programmatically call BO.add().



I have two projects referencing two different libraries/tables with primekeys of different data types exhibiting the same behavior.



Any ideas? Please see the attached error image, I cant seem to add images to posts anymore.

Keith Chisarik

That was it, I didn't set the default value for the primekey field. Your the man.



So then would the process be to always set the primekey field to a default, and then make sure to update it with the "real" primekey before calling save?



I was going to use my old VFP way of tracking primekeys that we used before VFP supported auto increment fields, have a table that has a record for each table in the database that contains a field for the next valid primekey.



I cant believe DB2 doesn't have auto increment fields in 2007.....



Thanks again for your help. So simple once you know......




Keith Chisarik

Well, this is kindof a trick question.  You must have the initialization of the properties turned off for the BO, otherwise this would have at least had a "0" in it when created.  So in this case, you will have to assign a value or manage the NULL value.  In this particular case, I think that I would go ahead and use a NextID table, like you did in VFP, and assign the "real" PK value in the SetDefaultValues of the BO.