[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: Using Progress.Data.BindingSource for non-GUI Purposes (on Windows)

  • Thread starter Thread starter dbeavon
  • Start date Start date
Status
Not open for further replies.
D

dbeavon

Guest
Yes, GetItemProperties(null) gets the schema details about the three TT columns, which the ProBindingSource can then use for updating the TT records from .Net. This is not the whole picture. Ultimately I'm trying to query data out of an ODBC connection (OdbcConnection) using a SQL statement, and then send it back over to the ABL session for follow-up processing. I was hoping to do that with one fast round-trip to a custom method in a .net assembly. I was hoping everything could be done very quickly. Otherwise it defeats the purpose of using an ODBC connection in the first place (because all the performance benefits of using ODBC would be lost once again while transferring this data back into ABL). I don't think probindingsource is a good fit for this scenario. The fastest approach seems to be for me to EXPORT it all to a file from .Net code, and then IMPORT it all back into the ABL side of things. This seems to have low CPU and memory overhead, compared to some of the other options I've looked at. I'm hoping that EXPORT/IMPORT will give me at least 5 to 10,000 rows per second. I guess we'll find out!

Continue reading...
 
Status
Not open for further replies.
Back
Top