Ok thanks, I can take that directly to my "higher up" and get some breathing room

Keith Chisarik

We do not have a timetable on this at the moment.  This may end up requiring a bit of work.  We will discuss this at our next development meeting.  Just so you know, we (the developers) are not in total control of our schedule...which is the way any successfully run business should be .  So we have to report to some "higher-ups" who will make the ultimate decision as to when this goes on the schedule. 

any word/timetable? Thanks.

Keith Chisarik

Any luck with this? Getting the BO Mapper to "see" the DB2 "tables" with the OLE Provider?


Keith Chisarik

I think that the IBMDA400 is correct for the OLE DB provider, however, I think that the GetSchema() method of the OleDbConnection object requires different parameters than other OLE DB providers.  Where with FoxPro, we use GetSchema("TABLES"), I don't think we can use "TABLES" as a parameter, because the database does not have "TABLES" but files. So, I think you're right on with your use of the DataDirect provider for creating your As400DbDataSourceItem class, but with the BOMapper, I think we're going to have to figure out what constraints we can use with the GetSchema() method to enumerate the database objects.

You are correct.  You will need to use the OLE DB provider for the BO Mapper portion.  You can use their ADO.NET provider for run-time purposes.  That is why you need to learn the OLE DB provider type.  The nice thing here is that you will not need to distribute the OLE DB provider in this case, just get it working on your development machine. 

In either case, just create a simple text program that creates an OleDbConnection and then call the Open...just keep changing out the provider until it works.  This is easier than going in and out of the BO Mapper.  I cannot give you the information for the provider since I am not familiar with this data provider, but I do know that the provider is where your problem is.

Here is how I tested using their sample code. It worked.



Dim conn As DDTek.DB2.DB2Connection



conn = New DDTek.DB2.DB2Connection("host=192.168.42.xxx; User ID=xxxxxx;Password=xxxxxx;database=xxxxxx)



Try

conn.Open()

MsgBox("good")

Catch ex As DDTek.DB2.DB2Exception

MsgBox(ex.Message)

End Try



conn.Close()



I was under the impression that I could use SF with the OLE string in the mapper as long as it referenced the DB2 provider. If that isnt the case, how do I implement SF with their ADO object? If I cant use the BO Mapper doesnt everything fall down?



I got the OLE to work using Provider=IBMDA400, its just doesnt enumerate the table names correctly, and its slow.




Keith Chisarik

When you use the DataDicrect provider in code, do you create an OleDbCommand object, or is it a Db2Command object from one of their namespaces?

I was under the impression that their provider was not an OLE DB provider, but actually a native ADO.NET provider, with its own classes and everything.

Well, that is much closer to a provider name since it is in COM class name or program ID format.

DataDIrect had me try DDTek.DB2..........

Keith Chisarik