Performance problem resulting from data conversion

We have a PC-.NET application and an eServer as a File Server connected over OLEDB/IBMDA400. We have very poor performance. In the trace (ibmda400.trc), I've seen that the eServer spent most of the time for the conversion of data fields sending them back to the PC. Is ODBC the better solution? How can I force the conversion?
I don't think you will find the performance of ODBC better then the ADO. We never came across performance problem resulting from conversion of data.

In ODBC (different provider) the data comes as EBCDIC to windows and translation is done there -- unless your data is Unicode and then you will need the translation.

Try with ODBC, and optimize as follows:

* Check the SQL statements to be optimized.
* Use blocked statements in ODBC (Click here for a good resource)
* Use the ODBC performance tab to define packages usage.

==================================
MORE INFORMATION ON THIS TOPIC
==================================

Ask your systems management questions--or help out your peers by answering them--in our live discussion forums.

The Best Web Links: Tips, tutorials and more.

Check out this Search400.com Featured Topic: Networking and the iSeries

PC/Windows connectivity expert Shahar Mor is available to answer your toughest networking questions. Ask Shahar a question or read his previously answered questions here.