I really don't have much exposure with ODBC. My initiatives of using
dblib was come from some of the samples in SQLPTK. Except spending
two to three days to figure out a few tricks behind it, all works fine
after this. To my impression, dblib handles query dynamically without
having the necessity to explicitly specify 'Prepare', that sort of SQL
statements. I can imagine that there must be some overhead behind,
but it has its beauty where I do not have to recompile my program after
a database change. ?However, it sounds like ODBC?is the way to go to compromise
with standard, I shall keep in mind in the future development.
<BLOCKQUOTE TYPE=CITE>MSFT has taken the position that ODBC is the standard
method of connecting
<BR>to SQL Server. In my own experience, I've found that the current
<BR>as fast or faster than DBLIB and much easier to work with, especially if
<BR>you are working with VB, Access, Active Server Pages, etc.
<BR><I>> I am building an application on the Internet using SQLServer.
<BR><I>> whether there are any difference between using dblib calls and
<BR><I>> calls in accessing the database, in term of efficiency, concurrency,
<BR><I>> any other concerns. Thank you in advance for any advice.</I>