On 1/27/2012 5:47 AM, Christof Wollenhaupt wrote:
> Hi Mike,
> The connection is busy while the query is still executing. You therefore
> need a separate connection for each query or send multiple statements in
> one batch if the server supports this. This could be an issue if you have
> transactions open or read from the same tables, as you might not see data
> on a different connection or run into a locking issue.
>
> If you have code that generically queries the return value of SQLEXEC(), be
> aware of the value 0 indicating that it is still executing. You won't get
> back 1 as usual.
>
> The cursors are created before the function returns for the first time, so
> you can safely bind controls and grids. However, as the cursor is filling
> in the background you should not call any function that requires the cursor
> to be fully available. That is, no RECCOUNT() call, no GO BOTTOM, COUNT
> FOR, etc. Otherwise you end up in a blocking situation. There's a
> CURSORGETPROP() call to retrieve the number of records in the cursor.
>
> SQLEXEC() only returns when the server has reported the structure of the
> resulting cursor. Some do this right after sending the statement, some
> along with the first batch of data. If the time consuming part is therefore
> preparing data on the server side due to aggregate functions or sorting the
> result cursor, you might not see a lot of performance improvement.
>
> Christof


Sounds like more of a PITA (Pain In The Arse) than it's worth.  Thanks 
for the tips.


-- 
Mike Babcock, MCP
MB Software Solutions, LLC
President, Chief Software Architect
http://mbsoftwaresolutions.com
http://fabmate.com
http://twitter.com/mbabcock16

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to