The hstmt error is endemic to odbc. It is caused by having more than one
active query at a time (an active query is one which has not retrieved all
it's rows).
To mitigate this try the following:
For queries, do a FetchAll in the OnOpen event.
Use multiple database components.
Use multiple
2001 22:56
To: Multiple recipients of list delphi
Subject: RE: [DUG]: Interbase X SQL Server
The hstmt error is endemic to odbc. It is caused by having more than one
active query at a time (an active query is one which has not retrieved all
it's rows).
To mitigate this try the following
Paul
This is an endemic MS SQL ODBC Problem, It is solved (sort of) in ADO
which adds connections as required (this of course chews up connections)
Have you considered ADO Express? I'd suggest Client side/Static Cursor
Datasets
as being the most reliable
HTH
Neven
- Original Message
Hi Paul
I've only seen this where the application is threaded and then it can be
solved (BDE) by giving each thread an independent session.
As to the date format error, check the ShortDateFormat. You may have to
coerce the date into a dd-mmm- or mmdd format. SQL 7 is set up by
default
