Very Computer

> --    CREATE TABLE LOG (TEXT CHAR(50))    --    the table LOG should be
> created before running the script
> DELETE FROM LOG


> BEGIN


> END
> INSERT INTO LOG VALUES ( 'END OF PROCEDURE' )

> After running this procedure I would expect to find 201 records in LOG
> table (and the last record should read 'END OF PROCEDURE')
> That was true when no ODBC driver was involved (I used Query Analyzer)
> But when I used ODBC client ( Foxpro or VB6 app ) I only could find 151
> record in the table LOG.  I tried 2 SQL Server ODBC drivers: Microsoft
> and MERANT and both had the same problem.  I have SQL Server 7.0
> (Service Pack 2 applied) installed locally on Windows NT 4.0 workstation
> (I selected "desktop version" when was running SQLServer installation)
> Any ideas?

> Thanks Greg

> --    CREATE TABLE LOG (TEXT CHAR(50))    --    the table LOG should be
> created before running the script
> DELETE FROM LOG


> BEGIN


> END
> INSERT INTO LOG VALUES ( 'END OF PROCEDURE' )

> After running this procedure I would expect to find 201 records in LOG
> table (and the last record should read 'END OF PROCEDURE')
> That was true when no ODBC driver was involved (I used Query Analyzer)
> But when I used ODBC client ( Foxpro or VB6 app ) I only could find 151
> record in the table LOG.  I tried 2 SQL Server ODBC drivers: Microsoft
> and MERANT and both had the same problem.  I have SQL Server 7.0
> (Service Pack 2 applied) installed locally on Windows NT 4.0 workstation
> (I selected "desktop version" when was running SQLServer installation)
> Any ideas?

> Thanks Greg

> actually it doesn't seem to be an ODBC problem - Query Analyzer also uses
> ODBC, OLEDB, or kind of (DB-lib is not in native use anymore).

> It should be a buffering problem with your data access method (RDO, ADO,
> etc.). By the way: do you perform the interaction in the client tool (I
> think this is true!), or do you just call the procedure (compiled at the
> server) from the client tool?

> J->

> > I am having a strange problem running the following anonymous procedure
> from
> > ODBC client:

> > --    CREATE TABLE LOG (TEXT CHAR(50))    --    the table LOG should be
> > created before running the script
> > DELETE FROM LOG


> > BEGIN


> > END
> > INSERT INTO LOG VALUES ( 'END OF PROCEDURE' )

> > After running this procedure I would expect to find 201 records in LOG
> > table (and the last record should read 'END OF PROCEDURE')
> > That was true when no ODBC driver was involved (I used Query Analyzer)
> > But when I used ODBC client ( Foxpro or VB6 app ) I only could find 151
> > record in the table LOG.  I tried 2 SQL Server ODBC drivers: Microsoft
> > and MERANT and both had the same problem.  I have SQL Server 7.0
> > (Service Pack 2 applied) installed locally on Windows NT 4.0 workstation
> > (I selected "desktop version" when was running SQLServer installation)
> > Any ideas?

> > Thanks Greg