Have a look at this topic in the SQL Server 2000 Books Online, it gives the
effects of connecting early version clients with SQL Server 2000:
DB-Library was frozen in SQL Server 6.5, so does not support some of the
features introduced in SQL Server 7.0 or SQL Server 2000.
Alan Brewer [MSFT]
Lead Programming Writer
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
Reading the book on line, I see that using sp_executesql
procedure can apport a lot of benefit to sql server, but
also to application that can receive that more faster rather
than execute (and rebuild) every time the comple sql
I'd like to implement the execution of sp_executesql under
vb, but question now is "How implement it?".
I suppose better (and probably only) way is to use
the command object and pass to recordset a command
object and its commandtext properties.
Is there on the net some samples, or hve you got one?