<div>
Assuming you are using the VB &quot;declare&quot; keyword to access the ODBC API, I would think that the speed difference in calling ODBC functions would be very small.<br />
<br />
My reasoning: the ODBC API is implemented in a set of DLL's and the overhead of calling a DLL function in VB is pretty small (compared to VC). In this case, it will have to convert from BSTR to char* for some API calls, but this isn't too costly a procedure.<br />
<br />
However, if you use the Jet engine to access the ODBC data source, you may find VB is slower. As ever, it depends on the program.<br />
<br />
As KangaRoo pointed out, in most DB programs the DB activity is the bottleneck - not the API calls.<br />

</div>


Assuming you are using the VB "declare" keyword to access the ODBC API, I would think that the speed difference in calling ODBC functions would be very small.

My reasoning: the ODBC API is implemented in a set of DLL's and the overhead of calling a DLL function in VB is pretty small (compared to VC). In this case, it will have to convert from BSTR to char* for some API calls, but this isn't too costly a procedure.

However, if you use the Jet engine to access the ODBC data source, you may find VB is slower. As ever, it depends on the program.

As KangaRoo pointed out, in most DB programs the DB activity is the bottleneck - not the API calls.


<div>
<div class="content wysiwyg-content">
Given the same set of ODBC APIs, is there any tangible speed difference in VC++ compared to &nbsp;VB?<br />

</div>
</div>


Given the same set of ODBC APIs, is there any tangible speed difference in VC++ compared to  VB?


ODBC API speed question

C++ is an intermediate-level general-purpose programming language, not to be confused with C or C#. It was developed as a set of extensions to the C programming language to improve type-safety and add support for automatic resource management, object-orientation, generic programming, and exception handling, among other features.