|
Home > Archive > MS SQL Server ODBC > January 2006 > key violation, general sql error, connectin busy with another hstmt
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
key violation, general sql error, connectin busy with another hstmt
|
|
| Doug Stephens 2006-01-12, 8:23 pm |
| We are getting this error periodically in a large app we are converting
from Access to SQL Server 2000. It uses BDE and ODBC for data access
and TTable/TQuery as well as TwwTable/TwwQuery components (from
woll2woll) under Delphi 6. It appears to happen when we are executing
TQuery.Open.
From what I've read, this is caused by ODBC not completing a result set
before processing another request. Which might be caused by having
queries run in multiple threads, but this is not the case.
| |
| Arnie 2006-01-13, 11:23 am |
| "Doug Stephens" <dougstephens@rogers.com> wrote in message
news:%23OgCxf7FGHA.1396@TK2MSFTNGP11.phx.gbl...
> We are getting this error periodically in a large app we are
> converting
> from Access to SQL Server 2000. It uses BDE and ODBC for data
> access
> and TTable/TQuery as well as TwwTable/TwwQuery components (from
> woll2woll) under Delphi 6. It appears to happen when we are
> executing
> TQuery.Open.
>
> From what I've read, this is caused by ODBC not completing a
> result set
> before processing another request. Which might be caused by
> having
> queries run in multiple threads, but this is not the case.
Basically, you can't have two open (SELECT) statements on the
same connection. For example,
Open query 1
Get some info from a record
Use that to set params in query 2
Open query 2 -- This will fail
This assumes both statements are attached to the same hDBC. It
is a result of using a client-side cursor for the hStmt's.
You'll have to use server-side cursors for the statements to make
this work. See MSDN.
This is one way to force a server-side cursor:
SQLSetStmtAttr( m_hStmt, SQL_ATTR_CURSOR_SCRO
LLABLE,
(SQLPOINTER) SQL_SCROLLABLE, 0 );
Good luck,
- Arnie
| |
| Doug Stephens 2006-01-13, 11:23 am |
| So you can never have 2 open queries? I do that all the time, in one
thread. Maybe I'm not understanding. For example, this code works
fine, which creates 101 open queries:
----------------
procedure TForm1. ManyQueriesClick(Sen
der: TObject);
var qs : array[0..100] of TQuery ;
var q : Tquery;
var i : Integer;
begin
for i := 0 to 100 do begin
qs[i] := TQuery.Create(self);
q := qs[i];
q.databasename := 'WM';
q.SQL.Clear;
q.SQL.Add('SELECT * FROM CUSTOMERFIELDS');
statusbar1.SimpleText := 'Query ' + IntToStr(i);
q.active := true;
end;
for i := 0 to 100 do
qs[i].Free;
end;
| |
| Doug Stephens 2006-01-13, 1:23 pm |
| Arnie wrote:
> "Doug Stephens" <dougstephens@rogers.com> wrote in message
> news:%23OgCxf7FGHA.1396@TK2MSFTNGP11.phx.gbl...
>
> Basically, you can't have two open (SELECT) statements on the same
> connection. For example,
>
> Open query 1
> Get some info from a record
> Use that to set params in query 2
> Open query 2 -- This will fail
>
> This assumes both statements are attached to the same hDBC. It is a
> result of using a client-side cursor for the hStmt's. You'll have to
> use server-side cursors for the statements to make this work. See
> MSDN.
>
> This is one way to force a server-side cursor:
>
> SQLSetStmtAttr( m_hStmt, SQL_ATTR_CURSOR_SCRO
LLABLE, (SQLPOINTER)
> SQL_SCROLLABLE, 0 );
>
>
> Good luck,
> - Arnie
How can I run SQLSetStmtAttr from Delphi?
| |
|
| "Doug Stephens" <dougstephens@rogers.com> wrote in message
news:uVMztRHGGHA.2012@TK2MSFTNGP14.phx.gbl...
> How can I run SQLSetStmtAttr from Delphi?
You can't. It's an ODBC statement. The equivalent in Delphi
would be CursorLocation := clUseServer for TADO components.
Sorry, but I've totally forgotten about the BDE. It may use
server-side cursors by default.
The problem occurs in ODBC when nesting queries that use the same
connection handle. Open q1, read some field values, use these to
set params in q2 and then open q2. This last open will cause the
error. In theory, SQL Server 2005 has 'fixed' this 'feature',
though I haven't tried it yet.
- Arnie
| |
| Doug Stephens 2006-01-16, 9:23 am |
| I found a way to call this function in ODBC32.DLL from Delphi but what
is the hstmt?
| |
| Doug Stephens 2006-01-16, 9:23 am |
| We have same problem with 2005.
| |
|
| "Doug Stephens" <dougstephens@rogers.com> wrote in message
news:e3UtnUqGGHA.2000@TK2MSFTNGP15.phx.gbl...
> We have same problem with 2005.
What DB objects are you using with 2005?
- Arnie
| |
|
| "Doug Stephens" <dougstephens@rogers.com> wrote in message
news:OfWhHUqGGHA.2000@TK2MSFTNGP15.phx.gbl...
>I found a way to call this function in ODBC32.DLL from Delphi
>but what
> is the hstmt?
As far as I know, you'd have to be using ODBC directly rather
than the BDE. hStmt is the ODBC statement handle.
- Arnie
| |
| Doug Stephens 2006-01-16, 9:23 am |
| Uh, tables and indexes. No stored procs. Is that what you mean?
|
|
|
|
|