Ben Chase (09/05/2007)
OK, I have a test project for you to run so we can maybe figure out why that is failing. It's failing within the DB2Connection.GetSchema() method (you'd think IBM would know how to get the schema from their own database...). So, run the project, click the button on the top to populate the top grid with the installed data providers on your computer, then select the row for the IBM.Data.DB2 provider (that will be the InvariantName), enter the connection string, and click Get Data Types. You should get an error message giving you the exception message that you're getting in the BOMapper.
Then, try the other IBM provider you have installed. Your client should have installed another one that will be a version specific provider, something like IBM.Data.DB2.9.1.2 or whatever zSeries, something. Select that one and repeat the process. If you get the same error, then I don't know what to tell you. If you don't get the error and it populates the grid below with the data types, then I'll have to create a way for you to specify the provider rather than always using the generic provider.
Let me know. Thanks.I gave Alan a hand on this earlier today and it turns out that the particular database that was being connected to was DB2 v7. It's scheduled to be upgraded, but hasn't been yet. I tried to connect to DB2 v8 and DB2 v9 from his machine and everything worked fine.
A Google search turned up that it was a data type that wasn't supported by DB2 UDB CLI. After a quick call to our database team, we learned that the database was v7 and that the data type wasn't supported by that version.
Bottom line is that the SF objects are working correctly as long as you try to connect to the correct version.
We just weren't aware that there were still v7 databases out there anywhere.
Thanks for all the help!