Also, I did remove the code from bo.SetDefaultValues.



I miss my SQL Server right now.



Thanks.

Keith Chisarik

I went back to using non-incrementing keys so I could get some stuff done until you tell me what is wrong when using DB2 auto-incrementing keys.



Everything is working the way I want by manually updating a new primekey value in the SetDefaultValue method but I have some questions. we used to do this all the time in VFP but I don't see how it can work in a disconnected data model? If I am creating 5 records on Client A and 5 records on Client B since the data isn't committed to the server until the call to BO.save(), my primekey assignment will fall down since Client B will get the same "next primekey" value from the server until Client A commits their inserts. Hopefully this is a moot point since I really want to use good old server assigned keys but i thought it a vlaid question to ask.



Also, why would BO.save commit my inserts/updates to the server, yet return FALSE? That is happening to me now.






Keith Chisarik

You might expand on this one since the Save returns an enum value rather than a boolean (i.e. Successful, Failed, etc.)

OK I will look into that, any thoughts on my bigger problem, the use of auto-incrementing keys with a DB2 datasource?



Thanks.

Keith Chisarik

DB2 is not something I work in every day so before I can just throw an answer out there like I can for SQL Server or some of the other databases.  I will have to get it setup and play with it on my side.    I have not dug into the DB2 server to play with this...yet.  But we will look into it.  Sorry for the delay

No problem, thanks.



Enjoy poking around with DB2




Keith Chisarik

Looks like it's trying to insert a value into the PK field because you might still have the PrimaryKeyIsAutoIncremented = False set.  Set it back to its default of True and you should be able to save it fine.  The Db2DataSourceItem is designed to work with auto-incremented columns the same way as SQL Server, it just uses a different server function to retrieve the next assigned value (where SQL Server uses SCOPE_IDENTITY()).  So, it should be working.  Re-set that field back to True to get back to ground-zero for this post, where you got the InvalidCastException and we'll go from there. 

Ben, I did set it back to TRUE, I am 100% sure of it as I thought that was the problem from the start once I got my database auto-incrementing and tested it a few times over before posting.



Thanks.

Keith Chisarik

Can you send me the create script for the table, the .vb file and the .designer.vb file for the business object/table that is causing the problems?  Also send me the stack trace for the error that you're receiving after you got everything back to ground-zero.  I think I'm going to have to run it on this end to see what it's doing.

My client is not happy with the performance of the IBM DB2 Provider for .NET.



As I understand iy SF DB@ support is designed to work with the IBM Provider IBM.DATA.DB2.dll and wont work with other third party providers, is this correct?



They want to use this.



http://www.hitsw.com/products_services/sql400/dlsql400.html

http://www.datadirect.com/products/net/net_for_db2/index.ssp

Keith Chisarik