Eno Resultset Error Creating Cursor Handle

Swedish Traditional Chinese Turkish | Location All Other RegionsASEANAustralia/New ZealandBeneluxD-A-CHGreater ChinaLatin AmericaNordicTaiwanUK and IrelandUS and CaribbeanCountriesBrazilCanadaFranceIndiaItalyJapanKorea (South)Russian FederationSpain Embarcadero Home Watch, Follow, & Connect with Us Share This Communities Articles Blogs Resources Downloads Help Submit Translation Printer-friendly EDN » Delphi » Database Show All [All] Getting 'Error creating cursor handle' when using TStoredProc By: Borland Staff Abstract: This error occurs, because the application tried to execute an SQL statement and retrieve a to execute an SQL statement and retrieve a result set that did not exist. Problem: When using TStoredProc and try to execute an InterBase stored procedure the error 'Error creating cursor handle' is generated. Solution: This error is the message that accompanies an ENoResultSet exeception thrown by the BDE. This error occurs, because the application tried to execute an SQL statement and retrieve a result set that did not exist. When using TStoredProcs with InterBase execute procedures the application must use the TStoredProc.ExecProc method instead of the TStoredProc.Open method (or setting active property to true). (See Data Definition Guide for more information on execute stored procedures) Latest Comments View AllAdd NewRSSATOM Move mouse over comment to see the full text Reply Posted by Stephen Schaff on May 25 2004Getting 'Error creating cursor handle' when using TStoredProcI admit to small amounts of knowlege when it comes to stored procedures and TDataSets. But I am getting this message when I try to call .Active := true on my TDataSet NOT a TQuerry and NOT a... Rating Average rating: 2.5 Votes: 0 1 1 0 0 Rating: 1 2 3 4 5 1=Poor, 5=Excellent Download Trial Buy Now Download Delphi10 now! Webinars on demand! More social media choices: Delphi on Google+ @RADTools on Twitter Server Response from: ETNASC01 Copyright© 1994 - 2013 Embarcadero

insert into a table by using a query. I am using parameters to load the values into the query, and so I first close the query, then set the parameter values and then I call the open statement and I get the following error: Project *.exe caused exception class ENoResultSet with message 'Error creating cursor handle'. However, when I go into Enterprise manager and look at the data, my data did insert. Here is my query: INSERT INTO EQHistory(Eq_job_nbr, Eq_id_nbr, Eq_date, Eq_hours, Eq_phase, Eq_technician, Eq_task_code, Eq_month, Eq_comments, Eq_paperwork, Eq_nopaperwork, [User], Webtrans) VALUES(:contract, :id, :date, :hours, :phase, :tech, :task, :month, http://edn.embarcadero.com/article/25392 :comments, :paperwork, :nopaperwork, :username, :webtrans) Here is my code: DM.InsEqhistory.close; DM.InsEqhistory.ParamByName('Contract').AsString := contract; DM.InsEqhistory.ParamByName('id').AsString := id; DM.InsEqhistory.ParamByName('date').AsString := date; http://www.delphigroups.info/2/06/231946.html DM.InsEqhistory.ParamByName('hours').Asfloat := hours; DM.InsEqhistory.ParamByName('phase').AsInteger := phase; DM.InsEqhistory.ParamByName('tech').AsString := tech; DM.InsEqhistory.ParamByName('task').AsString := ''; DM.InsEqhistory.ParamByName('month').AsString := month; DM.InsEqhistory.ParamByName('comments').AsString := comments; DM.InsEqhistory.ParamByName('paperwork').AsString := paperwork; DM.InsEqhistory.ParamByName('nopaperwork').AsString := nopaperwork; DM.InsEqhistory.ParamByName('username').AsString := user; DM.InsEqhistory.ParamByName('webtrans').AsString := webtrans; DM.InsEqhistory.Open; DM.InsEqhistory.Close; Any help will be greatly appreciated. BTW, I am using SQL7.0, D4, BDE 5.11 -- Dwaine Horton York Strategic Accounts Programmer dwaine.hor...@york.com 800-438-4447x2318 704-357-3434(f) Russell Smit Delphi Developer Sat, 03 Jan 2004 21:20:47 GMT Re:ENoResultSet error message with error creating cursor handle Use .ExecSQL instead of .Open on the query Dwaine Horto Delphi Developer

Delphi 3.0 C/S. The proc works fine when I test it from Oracle SQL*Plus32. When I call it from Delphi I get the message "Error creating cursor handle". The proc does return a result set. It uses a cursor to move through a table, summing up a field, http://www.delphigroups.info/2/9e/253983.html then doing some calculations with that sum. I pass it one input field and get two output http://search.cpan.org/~vizdom/DBD-JDBC-0.71/JDBC.pod fields back. Are there any obvious things that people often overlook? Any help would be greatly appreciated. Thanks, Bruce Todd Bar Delphi Developer Wed, 18 Jun 1902 08:00:00 GMT Re:Oracle - Error creating cursor handle On 3 Feb 1998 eno resultset 20:32:20 GMT, "Bruce Dellaira" wrote: Quote> I'm having a problem trying to use an Oracle stored proc from Delphi 3.0 C/S. > The proc works fine when I test it from Oracle SQL*Plus32. When I call it > from Delphi I get the message "Error creating cursor handle". > The proc does return a result set. It uses a cursor to move through a > table, summing up a field, then doing some calculations with that sum. 1. Have you created a package that defines a cursor type? 2. eno resultset error Is your OUT variable in the proc defined as being of that cursor type? 3. In Delphi, is the OUT parameter defined as being of type Cursor? 4. Are you using Open instead of ExecSQL for the TStoredProc? -Todd Barry Bruce Dellair Delphi Developer Wed, 18 Jun 1902 08:00:00 GMT Re:Oracle - Error creating cursor handle Todd, Thanks for getting back. I changed the type designation of my input parameter from CHAR (which it is) to ACCOUNTING.PROJ_NUM%TYPE and that eliminated the "Error creating cursor handle" error. However, my cursor has a "select * from ......." and delphi gives me an error for that line and for the line in the executable section "for my_rec in my_cursor loop ". It gives me the Oracle error ORA-06502 -- PL/SQL:numeric or value error. (Keep in mind that this stored proc works fine when I run it from the Oracle SQL*Plus window) I'm not doing any conversions or assignments so I think I may still have a cursor problem. I saw an earlier posting of yours where you gave an example of creating a package to define the cursor. I tried it but get compilation errors, specifically PLS-00103 -- "Encountered the symbol "REFCURSOR" when expecting ........." If you've got any more suggestions I'm all ears. Thanks, Bruce Other Thread

this POD (1) CPAN RT New 9 Open 2 View/Report Bugs Module Version: 0.71 Source NAME SYNOPSIS REQUIRES DESCRIPTION CONNECTING Starting the server Setting up log4j Connecting to the server Specifying JDBC connection properties USAGE NOTES Reading long data Calling JDBC methods Closing cursors Character sets jdbc_error DBI to JDBC method mappings Statement parameters and column values NUM_OF_PARAMS implementation last_insert_id implementation DIAGNOSTICS Errors generated by the Perl driver Errors generated by the Java server TO DO SEE ALSO AUTHOR COPYRIGHT hsqldb COPYRIGHT NAME DBD::JDBC - JDBC proxy driver for the DBI module SYNOPSIS use DBI; $dbh = DBI->connect("dbi:JDBC:hostname=$hostname;port=$port;url=$url", $user, $password); # See the DBI module documentation. REQUIRES Perl 5.8.6 or higher DBI 1.48 or higher Convert::BER 1.31 Java Virtual Machine compatible with JDK 1.4 A JDBC driver log4j 1.2.13 DESCRIPTION DBD::JDBC is a Perl module which works in conjunction with a server written in Java to provide a DBI front end to a JDBC driver. The Perl module and Java server may be installed on different machines, as long as socket connections are allowed. The Java server portion is multi-threaded and supports multiple simultaneous connections. This driver currently supports JDBC drivers which implement the JDBC 1.22 interface. JDBC 2.0-compatible drivers are expected to work, but no JDBC 2.0 functionality is explicitly exposed via DBD::JDBC. The $h->jdbc_func method exposes additional JDBC and driver-specific methods. Only Java methods with primitive or String parameters and return types are currently supported in this way. The expected use for this module is as a DBI interface to databases with JDBC drivers but no DBI drivers. The implementation of this module was originally done for a non-SQL database in order to take advantage of the existing SQL parser in the database's JDBC driver. The Java classes provided with this module also allo